Incode · Rate Limits

Incode Rate Limits

The Incode Omni API applies tiered, token-bucket rate limits by endpoint weight. Document endpoints (SUPER_HEAVY, e.g. add/front-id, add/back-id, process/id) and facial recognition endpoints (HEAVY, e.g. add/face, process/face) are limited to roughly 1 request/second with a 5-token burst, while other endpoints (OTHER) allow about 100 requests/second with a 50-token burst. Requests are capped at a 10 MB request/response size and a 30-second timeout. Exact account-level limits are set per deployment and not fully reconciled here.

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

It captures 5 rate-limit definitions, measuring requests, bytes, and seconds.

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

Tagged areas include Identity Verification, Biometrics, KYC, Liveness, and Onboarding.

5 Limits Throttle: 429
Identity VerificationBiometricsKYCLivenessOnboardingRate LimitingQuotasThrottling

Limits

Document Endpoints (SUPER_HEAVY) account
requests
~1 request/second, 5-token burst
Applies to ID document endpoints such as add/front-id, add/back-id, process/id.
Facial Recognition Endpoints (HEAVY) account
requests
~1 request/second, 5-token burst
Applies to face endpoints such as add/face and process/face.
Other Endpoints (OTHER) account
requests
~100 requests/second, 50-token burst
Applies to remaining Omni endpoints.
Request / Response Size request
bytes
10 MB
Maximum request and response payload size.
Request Timeout request
seconds
30
Maximum processing time per request.

Policies

Token Bucket
Endpoint classes use a token-bucket model with steady refill and a burst capacity.
Backoff Strategy
Clients should implement exponential backoff with jitter and retry on 429 responses.

Sources