AbacatePay · Rate Limits

Abacatepay Rate Limits

The AbacatePay v1 REST API authenticates with a Bearer API key and applies per-account abuse-prevention rate limiting. Specific published numeric limits (requests per minute/second per key) are not documented in the public API reference and are not reconciled in this artifact. Clients should handle HTTP 429 responses and retry with backoff.

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

It captures 2 rate-limit definitions, measuring requests and transactions.

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

Tagged areas include Payments, Pix, Brazil, FinTech, and Developers.

2 Limits Throttle: 429
PaymentsPixBrazilFinTechDevelopersRate LimitingQuotasThrottling

Limits

Requests Per Key account
requests
see provider documentation
Per-API-key abuse-prevention throttling; no published numeric value.
Withdrawals Per Month account
transactions
see provider documentation
Not a hard API throttle but a pricing tier boundary - the first 20 withdrawals per month are billed at a lower per-request fee.

Policies

Bearer Authentication
All requests require a valid API key sent as a Bearer token; unauthenticated requests return 401.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Idempotency
Use externalId on withdrawals and process webhooks idempotently to safely handle retries.

Sources