Avalara · Rate Limits

Avalara Rate Limits

Rate limit posture for the Avalara AvaTax REST API and supporting services (Returns, CertCapture, E-Invoicing). Avalara enforces per-account throttles tied to subscription tier; the platform returns standard 429 / 503 codes and clients are expected to back off and retry. Numeric thresholds are not posted publicly.

Avalara Rate Limits is the machine-readable rate-limit profile for Avalara on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, serviceUnavailable, and serverError.

Tagged areas include Tax Compliance, Sales Tax, VAT, and Rate Limiting.

2 Limits Throttle: 429
Tax ComplianceSales TaxVATRate Limiting

Limits

AvaTax REST API account
varies
see Avalara support / subscription tier
Numeric per-second limits are not publicly posted; thresholds depend on the customer's AvaTax subscription size.
Sandbox sandbox-account
varies
lower than production
Sandbox is intended for integration development; sustained load testing should be coordinated with Avalara support.

Policies

Backoff Strategy
Avalara's developer guide recommends exponential backoff with jitter on 429 / 503 / 5xx responses; honor Retry-After when present.
Idempotency
Use the documented transaction code (CompanyCode + DocCode) so retried CreateTransaction calls return the existing transaction rather than creating duplicates.
Batch Where Possible
For high-volume reconciliation, prefer the Batch APIs over single-call CreateTransaction to minimize calls per transaction.
Avoid Sandbox for Load Testing
Sandbox carries lower thresholds than production; coordinate any load test with Avalara support to use a sized environment.

Sources