What's the Allocadia API rate limit?

100 calls per minute per user. Exceeding it returns HTTP 429. Use list endpoints, $filter, and caching to stay under.

The Allocadia REST API rate limit is 100 calls per minute per user. Allocadia counts every authenticated request, so a read-heavy integration making many small GETs hits the limit just as easily as a write-heavy one.

When you exceed the limit, you'll get HTTP 429 Too Many Requests. The standard response is to back off, wait at least 60 seconds, and retry — exponential backoff (60s → 120s → 240s) is conservative and reliable.

Patterns that help stay under the limit

• Use bulk/list endpoints (GET /lineitems with $filter) instead of looping single-ID GETs.
• Filter aggressively in the query rather than fetching broadly and filtering in your code.
• Cache reference data that doesn't change often (column choices, attribute definitions, user lists).
• Add a deliberate ~600 ms delay between calls to pace at ~100/minute without any backoff logic.

For the full guidance on backing off and redesigning when you're hitting 429s regularly, see Allocadia API requests returning HTTP 429 — too many requests.

Related articles

• Allocadia API requests returning HTTP 429 — too many requests
• The Allocadia REST API — overview of endpoints
• REST API authentication in Allocadia (bearer token, 20-minute timeout)