Qonto · Rate Limits

Qonto Rate Limits

Qonto applies request rate limitations per IP address across its Business API. Exceeding them returns HTTP 429 Too Many Requests. There is an additional throttle when too many authentication failures occur, which is why Qonto recommends proactively refreshing OAuth access tokens before expiry rather than reacting to 401 errors, and preferring webhooks over polling.

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

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

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

Tagged areas include Business Banking, Fintech, Payments, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Business BankingFintechPaymentsRate LimitingQuotasThrottling

Limits

Short-window request limit ip
requests · 10 seconds
1000
1,000 requests per 10 seconds per IP address.
Long-window request limit ip
requests · 10 minutes
10000
10,000 requests per 10 minutes per IP address.
Authentication-failure throttle ip
requests_401 · 1 hour
200
Throttling is applied if more than 200 requests returning HTTP 401 occur within 1 hour. Refresh OAuth access tokens proactively to avoid this.

Policies

Per-IP enforcement
Rate limitations are applied per IP address, not per token or per organization.
Proactive token refresh
Check access-token expiry and refresh before making calls instead of waiting for a 401, to avoid the authentication-failure throttle.
Prefer webhooks over polling
Subscribe to webhook events for real-time updates instead of polling endpoints.

Sources