Codat · Rate Limits

Codat Io Rate Limits

Codat applies per-client rate limiting across api.codat.io. When limits are exceeded the API returns HTTP 429 (Too Many Requests). Because Codat proxies and pulls from many underlying accounting, banking, and commerce platforms, the practical throughput of data-refresh operations is also bounded by the rate limits of those source platforms. Specific numeric thresholds are not publicly published and are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and pull_operations.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Business Data, Accounting, Banking, Commerce, and Fintech.

3 Limits Throttle: 429
Business DataAccountingBankingCommerceFintechRate LimitingQuotasThrottling

Limits

API Requests client
requests
see provider documentation
Per-client request rate on api.codat.io; exceeding returns HTTP 429.
Data Refresh (Pull) Operations company
pull_operations
bounded by source platform
Queued data refreshes are asynchronous; effective throughput is constrained by the rate limits of the connected accounting/banking/commerce platform.
Write Operations connection
requests
bounded by source platform
Push operations (Sync for Payables/Expenses, Bank Feeds) are subject to the target platform's own write throttling.

Policies

Asynchronous Pulls and Webhooks
Prefer webhook event subscriptions over polling. Codat notifies when a data type finishes syncing, avoiding tight polling loops against rate limits.
Backoff Strategy
On HTTP 429, clients should implement exponential backoff with jitter and honor any Retry-After header before retrying.

Sources