AutoTask.Psa.Api 1.1.22

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package AutoTask.Psa.Api --version 1.1.22
                    


                    

                
NuGet\Install-Package AutoTask.Psa.Api -Version 1.1.22
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="AutoTask.Psa.Api" Version="1.1.22" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="AutoTask.Psa.Api" Version="1.1.22" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="AutoTask.Psa.Api" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add AutoTask.Psa.Api --version 1.1.22
                    


                    

                
#r "nuget: AutoTask.Psa.Api, 1.1.22"
#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. 
#:package AutoTask.Psa.Api@1.1.22
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=AutoTask.Psa.Api&version=1.1.22
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=AutoTask.Psa.Api&version=1.1.22
                    


                            Install as a Cake Tool

License: MIT

Codacy Badge

AutoTask.Psa.Api

Datto Autotask PSA REST API

Nuget

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows 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
1.1.23 39 9/3/2026
1.1.22 49 9/3/2026
1.1.20 76 8/31/2026
1.1.19 79 8/31/2026
1.1.18 78 8/31/2026
1.1.16 103 8/28/2026
1.1.8 517 6/6/2026
1.1.7 189 4/29/2026
1.1.5 214 4/16/2026
1.0.45 9,532 12/20/2024
1.0.40-beta-gc85ed508b0 20,761 1/12/2023
1.0.35-beta-gd862e7b8a9 340 10/14/2022
1.0.21-beta-gd587bc4a05 475 1/21/2022
1.0.20-beta-gadef0dc0f2 638 12/6/2021
1.0.19-beta-g8df6a579c3 666 12/6/2021
1.0.16-beta-g3a72b88cb6 365 12/6/2021
1.0.13-beta-g3ea5f387f4 413 10/22/2021

Security fix: sensitive HTTP headers are now redacted in diagnostic output.

Previously AuthenticatedHttpClientHandler passed the request header collection straight to the
logger at Debug level. HttpHeaders.ToString() applies no filtering, so the three headers this
client authenticates with were written verbatim - including Secret, which carries the account
password in plain text. Any consumer running at Debug retained usable credentials for the life
of its log store.

Secret, UserName and ApiIntegrationCode are now redacted, along with Authorization,
Proxy-Authorization, Cookie, Set-Cookie and common API key header names, case-insensitively.
The credential length is retained, so requests remain diagnosable without exposing the value.

Consumers should upgrade and then review existing Debug logs for previously captured
credentials.

Also in this release: logging of response content when an exception occurs, which must be
enabled through the client options LogExceptionContent property.