iayos.intrinioapi 3.2.2

.NET Framework 4.6.1 This package targets .NET Framework 4.6.1. The package is compatible with this framework or higher. 
dotnet add package iayos.intrinioapi --version 3.2.2                

                    
                

            
NuGet\Install-Package iayos.intrinioapi -Version 3.2.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="iayos.intrinioapi" Version="3.2.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add iayos.intrinioapi --version 3.2.2                

                    
                

            
#r "nuget: iayos.intrinioapi, 3.2.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install iayos.intrinioapi as a Cake Addin
#addin nuget:?package=iayos.intrinioapi&version=3.2.2

// Install iayos.intrinioapi as a Cake Tool
#tool nuget:?package=iayos.intrinioapi&version=3.2.2

A strongly typed package to wrap the Intrinio FinTech data api (www.intrinio.com).
Author not affiliated with intrinio in any way, not does this come with any warranty. Contributions welcome.

Product Compatible and additional computed target framework versions.
.NET Framework net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
3.2.2 1,913 11/22/2016

Bugfix for broken date formatter whereby the StartDate_IaYoS and EndDate_IaYoS convenience properties didnt actually
parse correctly into a formatted date string (such as when trying to query historic price ranges, would erroneously
end up with string 'YYYY-08-DD' instead of '1980-08-14' for example