AvaTax Developer Blog Posts

Introduction to the Avalara AvaTax API

Anya Stettler has put together a nice video overview of the Avalara AvaTax API. It’s a great place to start learning the details you’ll need for a good integration. To find out more about the business use cases and features you should be thinking about, check out our Integration Checklist.

Developer Testimonial

Our Partner’s developers say integrating to AvaTax is a breeze. Try it today!  Sign up for our API Free Trial.

Handling Java SSL Certificate Exception

If you are trying to make an HTTPS call to the AvaTax web service from a WebSphere Message Broker  and recieve an exception message similar to below, it is likely that the Message Broker is unable to build the entire certificate path. The Message Broker “keystore” must have all of the certificates in the “chain” of CA’s. javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error One way...

Testing Address Errors

When you’re testing your integration, it’s always a good idea to figure out how you’re going to handle errors. Not all errors from our system are bad - some just mean a user has entered an invalid address (perhaps by making a typo!) - and your system should react accordingly. These address-related errors are to be expected in normal use of your connector. Sometimes it can be challenging to create this use case on purpose: our system is very good at validating addresses and calculating tax accordingly (albeit at lower precision levels). In fact, due to customer demand, we recently updated...

Reflecting MDET

At the beginning of 2013, a new federal-level excise tax was introduced for some medical devices. If you have clients that need to reflect this tax, make sure you’re doing the following: Allow clients to pass a product tax code. Allow clients to assign an Entity/Use Code (CustomerUsageType) to their customers. The combination of product tax code and customer entity/use code allows your client to trigger specific rules in their company profile, and calculate this tax. If you’re using service version 13.1 or later, you can parse out this tax from your GetTaxResult as well - it will come across...

Updates to REST tax/get POST with 13.3. release

Some long-awaited additional parameters have been added to the tax/get POST request with the recent 13.3 release. These parameters are now available on both development and production for all clients using the REST API. With this update, the REST API is now in full best-practice parity with our SOAP API. For more information, see the tax/get POST documentation. PosLaneCode Client BusinessIdentificationNo TaxOverride

SSL Certificate Update

Until recently, our development server was using a COMODO SSL certificate. We just updated to a Verisign one to match our production servers - documentation has also been updated to reflect the new certificate.

Ember.js event at Pier 55

Avalara has been using Ember.js for six months now so we were proud to host the inaugural Seattle Ember.js Meetup last Thursday. In a meeting that tested the capacity of our new space on the water at Pier 55 in downtown Seattle we were honored to host Yehuda Katz and Tom Dale from the core Ember.js team in a presentation that lasted two hours. In Avalara tradition we rolled out the margarita machine for the participants and the conversations with the presenters lasted well into the night. Yehuda and Tom delivered a wealth of information about the upcoming functionality in Ember...

Subscribe via RSS!