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, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests and transactions.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Payments, Pix, Brazil, FinTech, and Developers.
generated, dated 2026-06-21.
Limits
Policies
Sources
- https://docs.abacatepay.com/pages/authentication
- https://docs.abacatepay.com/pages/v1/introduction
- https://docs.abacatepay.com
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.