Avalara > Blog > Patch Updates > REST v2.17.2 Patch Notes

REST v2.17.2 Patch Notes

  • Feb 16, 2017 | Ted Spence

This article is about the February 2017 monthly update to the AvaTax REST v2 API.

Sandbox https://sandbox-rest.avatax.com 2017-02-23
Production https://rest.avatax.com 2017-02-27

Free Tax Rates!

Avalara is pleased to announce the freely available REST v2 TaxRates API! The TaxRates API provides basic tax functionality for no cost.

You also now have available an API that creates a free 30-day trial of AvaTax Professional. This free trial account comes with no obligations and allows you to experiment with a fully featured version of Avalara AvaTax. After 30 days, you may continue to use the free TaxRates API or you can upgrade to a full account.

For more information on using the free TaxRates API, please see Estimating Tax with REST v2.

Onboarding API in REST v2

With the release of 2.17.2, all functionality from the existing Onboarding API has been fully migrated to REST v2. Avalara will be deprecating the existing onboarding API, and will work with individual partners to assist them in upgrading to REST v2.

Jurisdiction Override API

For customers who have a need to fine-tune Avalara’s address resolution software, we provide the new Jurisdiction Override API. A jurisdiction override is a flag that tells AvaTax to calculate a specific address according to the rules of a slightly different nearby jurisdiction. This functionality is often useful when a company has set up business on the boundary between two tax regions and may need to request specific tax treatment if they have received a ruling from a tax authority that they should be using specific tax rules.

Customers have always had the ability to log onto Admin Console to create these overrides through a friendly web interface; this new API allows a customer to make these same adjustments via a programmatic interface.

Updated Returns APIs

Significant upgrades and functionality have been enhanced to Avalara’s Managed Returns Service API, including:

  • TaxAuthorityId information now available on filings
  • Filing status is now returns as an enumeration
  • Filings are now designated as accrual or filing types
  • Notices endpoint allows download of attachments
  • Filing request approval process bugfixes and enhancements

The managed returns APIs are available by invitation only.

Friendly Authentication in Swagger

We have updated to the latest release of API Documentation! You can tell we upgraded because the new color is Orange. One great side effect of the latest update is that we now support browser-based authentication both via Avalara Identity and username/password credentials! Here’s how it will work.

First, you click the Authorize button in the top right of the API reference screen.

Next, you can choose to either authenticate via OAuth 2.0 or Username/Password:

We recommend authenticating via OAuth 2.0, since it works using a unique bearer token that is valid for 30 minutes at a time. This token is automatically transmitted from Avalara Identity to the API server under a secure channel, so you can experiment with the swagger API without having to encode your username and password into a Base64 string.

When you click the OAuth 2.0 link, you’ll redirect to Avalara Identity, the new universal sign-on page for Avalara products:

Type in your username and password and click Login. You’ll be redirected back to the AvaTax API documentation, and all calls to the API will be fully authenticated. When your token expires, you’ll be redirected back to Avalara Identity to login again.

Lock Document API

Customers wishing to test the behavior of document locking will be able to use a new Document Lock API in sandbox. The document lock API will be available in production by invitation only.

Changes to Existing API

POST /api/v2/transactions/create

  • Date fields on the CreateTransaction API call now only show date, with no time information or time zone offset. This means that customers should see consistent behavior for the date of their API call regardless of the time zone in which they are calling the application.
  • In 2.17.1, it was possible to specify the tax date of a transaction in two different places: Both the root document level as taxDate, and also in the taxOverride.taxDate element. We have removed the taxDate element and standardized on taxOverride.taxDate. Code that transmits the taxDate element will have no effect on a transaction.
  • Some customers have expressed confusion about what happens when line-level address overrides are created on a transaction with more than one line. Avalara's policy is that overriding any one address on a line shall override all addresses on the line. This means that if you set the shipTo element at the document level, and then set the shipFrom element at the line level, the line level will not inherit the shipTo address from the document.
  • Customers wishing to override addresses for one line on a transaction must override all addresses for that one line. If you leave the line.addresses object null, it will inherit all addresses from the root document element.
  • Latitude and Longitude are now returned when creating or fetching a document.
  • The reportingLocationCode field on the document level is now correctly updated and returned in results.

GET and POST /api/v2/addresses/resolve

Address resolution APIs now also return an address type code indicating the type of address identified by our service.

POST /api/v2/companies/123/nexus

The nexus object has been updated to use dates only, with no time or time zone information. This prevents display problems where a nexus created in one time zone will behave differently in a different time zone.

Error messages for nexus creation have been updated to increase usability of nexus APIs.

GET /api/v2/companies/ABC/transactions

Listing transactions by company now returns a fully valid RecordsetCount value.

Results from transaction search APIs are delayed by 1-5 seconds from live data to reduce impact on production services.

GET /api/v2/companies/123/batches

Users fetching batches and batch files now no longer automatically download the batch files with each API call.

Users can use the new GET /api/v2/companies/123/batches/456/files/789/attachment API to retrieve the actual file for each batch. This allows users to download only the specific batch attachments that they wish to retrieve.

The content element in a batch object will now be null on retrieval.

Other Bugfixes and Improvements

  • Accounts with AvaTaxPro that do not have an AvaTaxST subscription now correctly work with transaction APIs
  • Batch service fileshare uptime tests updated

Sales tax rates, rules, and regulations change frequently. Although we hope you'll find this information helpful, this blog is for informational purposes only and does not provide legal or tax advice.
Avalara Author
Ted Spence
Avalara Author Ted Spence
Ted Spence is working as Director of AvaTax Core Engine at Avalara.