AvaTax API 17.9 Patch Notes
This article is about the August 2017 monthly update to the AvaTax API.
License Key Authentication Update
The AccountResetLicenseKey API will now return an
AccountInNewStatusException error if your account has not yet been activated by reading terms and conditions on the AvaTax website. Please note that resetting your license key will invalidate all previous license keys for your account. AvaTax will send an email to all active account administrators for your account notifying you that the license key was reset.
Activating your account using the ActivateAccount API will no longer automatically generate a license key.
Asynchronous Reporting API
In order to ensure reliable performance of report generation using the Reporting API in REST, we have enforced a rate limit on report requests so that concurrency issues do not delay or block report generation.
The Reporting API has been split up as follows:
- Request a report using the
InitiateAPI. You will receive back a report ID number.
- Check status on a report by requesting it via the
GetReportAPI, and pass in the report ID number you received from the
InitiateAPI call. When a report is ready for download, the status will show
- Download the actual report file using the
The synchronous reporting API has been deprecated.
Improvements to the CreateTransaction API
A variety of improvements were made to the CreateTransaction API.
- Improved performance and reduced data store usage provide more consistent performance, even during busy hours
- Updated documentation helps to explain how it relates to [CreateOrAdjustTransaction](https://developer.avalara.com/api-reference/avatax/rest/v2/methods/Transactions/CreateOrAdjustTransaction/) so users can more freely decide between the two APIs.
- The field Description will now be returned correctly when getting estimates using the SalesOrder transaction type.
- Customized error message for when you use only destination or origin address types with a transaction.
- The SalesOrder transaction type now supports $include=SummaryOnly.
- The SalesOrder transaction type now correctly obeys the TaxDebugLevel parameter. In version 17.8.1, it returned diagnostic-level detail for all sales orders regardless of the setting of the TaxDebugLevel parameter.
- Fixed an unhandled exception that occurred rarely when modifying an existing transaction.
Other Bugfixes and Improvements
- Improved error messages for CreateUser API; users can be set to NoAccess privilege levels.
- Additional logging and metrics for users seeing unhandled exceptions.
- Improved documentation for a variety of APIs.
– Ted Spence, Director, AvaTax Core Engine