Fazz · Rate Limits

Fazz Rate Limits

The Fazz Payments API documents that rate limiting is enforced on API requests (a "Rate Limiting" resource is listed in the developer docs), but specific per-endpoint request-per-minute thresholds are not published on the public pages. Clients should handle throttling responses and retry with backoff. Idempotency keys are supported to make write requests safely retriable.

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

It captures 1 rate-limit definition, measuring requests.

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

Tagged areas include Fintech, Payments, Disbursements, Rate Limiting, and Quotas.

1 Limits Throttle: 429
FintechPaymentsDisbursementsRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Rate limiting is enforced per account; specific RPM thresholds are not published publicly.

Policies

Idempotency
Write requests support idempotency keys so retries do not create duplicate payments or disbursements.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.

Sources