Avalara Developer Network Developer blog

AvaTax Developer Blog Posts

Geocoding in REST v2

The tax on your transactions is heavily dependent on where the transactions occur. In the US sales and use tax world, transactions are generally taxed based on either the “Origin” or “Destination” - but for most retail sales, these two addresses are almost always the same. When you visit your local grocery store, they charge you a single rate based on product type and the location of the store; but if you place an order online, the tax you pay will be influenced by a number of factors including the origin location of the warehouse and the destination address where...

Estimating Tax with REST v2

The AvaTax REST API provides lots of different levels of estimated tax values, and sometimes it may be hard to know the right way to estimate tax for your customers. For today’s blog article, I will be walking you through the different types of estimates that are available in AvaTax REST v2 and how they can help you. AvaTax is of course built on correctly identifying the exact tax amounts for an invoice; and to do this, we incorporate dozens of factors including the origin and destination address, dollar amounts, taxability rules, nexus declarations, registration rules, customer exemption certificates, and...

REST v2.16.11 Patch Notes

REST v2.16.11 Patch Notes AvaTax REST v2.16.11 has now adopted the naming system used by AvaTax SOAP (API version/year/month). Environment URL Release Date Sandbox https://sandbox-rest.avatax.com 2016-11-02 Production https://rest.avatax.com 2016-11-09 POST /api/v2/taxrates Corrected a bug that caused the TaxRates API to show duplicate rates. POST /api/v2/transactions/create New fields have been added to the API. These fields are optional and do not require changes to your existing code. Added new fields on the create transaction model: debugLevel (string, optional): If the user wishes to request additional debug information from this transaction, specify a level higher than 'normal'. Enum, possible values = ['Normal',...

Batched Transactions in REST v2

Uploading Batched Transactions One of the most common inquiries we get at Avalara is about the need to reconcile, or publish, a full list of a company’s transactions at the end of the month. Many businesses work by cash register day by day, and at the end of each month they produce a report listing all the transactions that they processed. Sometimes businesses will have one report for each location, or cash register, or salesperson; and they need a batch process they can use to upload all of these transactions into AvaTax for later reconciliation, or for filing tax returns....

REST v2.3.1 Patch Notes

REST v2.3.1 Patch Notes For those of you who participated in the AvaTax REST v2 Preview program, I’d like to take this opportunity to thank you for your time and effort helping us debug a huge software release. We’ve now implemented a clean, modern, consistent REST API that covers tax functionality from top to bottom - and we’ve established a great platform for continuing improvements. Now that the program is winding down, please take note of a few differences between the final release of REST v2 and the preview program you tested in August/September: New URL for REST v2 The...

LandedCost with REST v2

Updated March 22, 2018 - AvaTax REST has a new syntax for making LandedCost calculations. This post is retained for historical purposes. You may read about the new LandedCost integration at https://developer.avalara.com/blog/2018/03/22/calculate-customs-duties-in-rest/. Selling Cross-Border With the release of the LandedCost calculator functionality, AvaTax now provides features to help you sell across country borders. LandedCost will help you identify customs duty for various types of harmonized tariff codes. Once you’ve begun using AvaTax REST v2, you’ll have to make a few minor changes to begin using the LandedCost calculator. Here’s what you need to know. Harmonized Tariff Schedule (HTS) For every...

Filtering in AvaTax REST v2

I'm sure I left this somewhere... The REST API pattern is designed to make it easy to store and retrieve data. Every piece of data in REST is assigned a single unique URL - and you can always fetch that item back by retrieving its URL. It works a bit like this: Request POST /api/v2/companies { "name": "Bob's Artisan Pottery" } Result In the result headers, you’ll get back this response that tells you the URL of your newly created object: Location: /api/v2/companies/123 Then, when it’s time to fetch something back, you can retrieve it back using that location, and...

Getting Started with AvaTax REST v2

It's time to make taxing more relaxing! Over the next fifteen minutes, I’ll walk you through the process of using Avalara’s V2 REST API to implement a simple web-based eCommerce platform. We’ll show you how to request an account, set up a company, and process tax for that company. Everything we will do today can be fully scripted - so as soon as you’ve gone through this demo, you’ll be know everything you need to add transactional taxes to your platform. For today, we’ll set up the company “Bob’s Artisan Pottery”, an online store that sells mugs. As Bob McExample,...

Subscribe via RSS!