Signzy · Rate Limits

Signzy Rate Limits

Signzy does not publish specific public rate-limit numbers. Throughput is governed per-account by the commercial agreement and access token, and the preproduction / sandbox environment carries lower quotas than production. Access tokens issued by /api/customers/login are short-lived (a `ttl` in seconds) and must be refreshed. Specific per-endpoint request-per-minute values are not documented publicly and are not reconciled here.

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

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

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

Tagged areas include Identity Verification, KYC, Compliance, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Identity VerificationKYCComplianceRate LimitingQuotas

Limits

Per-account throughput account
requests
see commercial agreement
Governed by contract and access token; not published.
Token TTL token
seconds
see login response ttl
Access token from /api/customers/login expires after its ttl; re-login to refresh.
Sandbox quota environment
requests
lower than production
Preproduction host api-preproduction.signzy.app carries reduced quotas for testing.

Policies

Token Expiry
Access tokens are short-lived; clients must re-authenticate when ttl elapses.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429.

Sources