Pagar.me · Rate Limits

Pagarme Rate Limits

The Pagar.me Core API (v5) enforces per-account request rate limits to protect platform stability. Specific published thresholds (requests per minute/second) are not enumerated in the public reference and vary by account and endpoint; callers exceeding limits receive HTTP 429. Pagination on list endpoints is controlled with page and size parameters. Specific per-endpoint values are not reconciled in this artifact.

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

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

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

Tagged areas include Payments, Payment Gateway, PIX, Boleto, and Brazil.

2 Limits Throttle: 429
PaymentsPayment GatewayPIXBoletoBrazilRate LimitingQuotasThrottling

Limits

Requests Per Account account
requests
see provider documentation
Per-account request throttling; specific RPM/RPS not publicly enumerated.
List Pagination Size endpoint
items
page / size query parameters
List endpoints paginate via page and size; size has a provider-enforced maximum.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.
Idempotency
Use idempotency keys on charge/order creation to avoid duplicate payments when retrying.

Sources