Server and installation requirements

This section provides requirements for including calls made from the integration and for demonstrating/documenting the software installation process.


Requirement	Use case	Endpoints/Models	Type
Pass integration identifier information	Users must include information about the connection as a signature in each transaction.	N/A	Required
Consume and display error messages from API responses	Users must ensure that the integration doesn’t include messages (errors, warnings, and so on) except those that would result from normal (but not valid) user input (for example, incorrect address data). In addition, these messages must be logged/displayed appropriately in the application.	N/A	Required
A reasonable ratio of calculation and address validation calls to committed documents	Users must ensure that the integration minimizes traffic. AvaTax will expect to see up to approximately 10 calculations per finalized document (including for abandoned carts). Failing to do so will drive up usage and billing. You can also provide a simple "estimated tax" option, just ensure that the estimate doesn’t call to AvaTax.	N/A	Required
Demonstrate and document installation of software	If there’s something to install on the source application, then you must demonstrate and document that process.	N/A	Required