Unit · Rate Limits

Unit Co Rate Limits

Unit enforces rate limiting on the API - Unit's Help Center confirms a documented "What is Unit's rate limit?" article exists, and Unit's API reference describes filtering/paging controls (page[limit], page[offset]) on list endpoints - but this research pass could not independently re-confirm the exact numeric request-per-minute/second ceiling from a live docs page (the specific rate-limit reference page returned a 404 at review time, and the figure is not present in Unit's published OpenAPI specification). Treat any specific number as unverified until confirmed directly with Unit.

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

It captures 4 rate-limit definitions, measuring requests, records, and attempts.

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

Tagged areas include FinTech, BaaS, Banking, Rate Limiting, and Quotas.

4 Limits Throttle: 429
FinTechBaaSBankingRate LimitingQuotas

Limits

API Request Rate org
requests
not independently confirmed in this research pass
Unit's Help Center references a "What is Unit's rate limit?" FAQ; a prior, unreconciled note in this network cites 1000 requests/minute per IP. Verify current numeric limits with a Unit solution engineer.
List Endpoint Page Size request
records
configurable via page[limit] (default varies by endpoint; overall paging is offset-based)
Applies to list endpoints such as GET /applications, GET /accounts, GET /events, GET /transactions.
Customer Token Verification Attempts customer
attempts
bounded (documented as a small number of attempts per short window in Unit's customer-token verification flow)
Exact figures not reconciled in this pass; see Customer API Tokens documentation.
Sandbox vs Production environment
requests
differ by environment
Unit's own materials indicate sandbox and production throttling are configured independently; production limits are set per BaaS agreement.

Policies

Backoff Strategy
Implement exponential backoff with jitter on HTTP 429 responses.
Idempotency
Attach an idempotencyKey to POST requests that create resources (applications, accounts, payments) to safely retry after a timeout or 429 without creating duplicates.
Scoped Tokens
Use short-lived, narrowly-scoped Customer API Tokens for end-user initiated actions instead of the broader org API token, reducing blast radius and typically the applicable throttling scope.
Paging
Use page[limit] and page[offset] (and, on Events, filter[since] / filter[until]) to pull large result sets in bounded pages rather than requesting unbounded lists.

Sources