Avalara AvaTax vs TaxCloud

Avalara AvaTax

The REST API has a public Swagger file with 491 operations, a Markdown page per endpoint and a 90-day trial with no card. Production rate limits and prices per transaction are not published, the API patch notes stop at April 2023, and the tax calculation service was degraded for about 23 hours on 5 and 6 October 2026.

TaxCloud

A 30-operation REST API with a public OpenAPI 3.1 contract, llms.txt, Markdown docs and a 30-day trial that needs no card. The vendor publishes no rate limit numbers, no SLA, no API changelog and no official v3 client library, and the security page names no audit or certification.

Avalara AvaTax

1. Omit type or send SalesOrder for an estimate. A type ending in Invoice is recorded, and commit set to true locks it for reporting
2. Retry a timed-out invoice with CreateOrAdjustTransaction, not CreateTransaction, which errors when a committed transaction has the same code
3. Use sandbox-rest.avatax.com with sandbox credentials for tests. Production is rest.avatax.com and the two accounts are separate
4. Add $include=SummaryOnly or LinesOnly to shrink transaction responses, and page lists with $top (1,000 at most) and $skip
5. Call /api/v2/utilities/ping first. It answers without credentials and shows whether the credentials sent were accepted

TaxCloud

1. Send X-API-KEY on every call and put the connection ID in the path, as in /tax/connections/{connectionId}/carts. A wrong ID returns 404
2. Mark nexus states active in the account first. With none active the API returns zero tax and no error
3. Use a separate test connection. There is no sandbox, and orders on a live connection go into filing
4. Pass a stable idempotencyKey on refunds, and never convert the same cart twice. A second conversion creates a duplicate liability
5. Void a wrong order before 12:00 AM Eastern on the 10th of the month after its completedDate. Later requests return 422