Conekta · Rate Limits
Conekta Rate Limits
Conekta does not publish explicit per-second or per-minute rate limits in its developer documentation. The platform implements internal throttling and antifraud rules per merchant. High-volume merchants should coordinate with the Conekta integrations team and rely on idempotent webhook retries rather than client-side burst loops.
Conekta Rate Limits is the machine-readable rate-limit profile for Conekta on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests_per_minute and retries.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serverBusy.
Tagged areas include Rate Limiting, Payments, and Mexico.
2 Limits
Throttle: 429
Rate LimitingPaymentsMexico
Limits
Per-merchant API request rate account
undisclosed
Webhook delivery retries webhook
18
Policies
Idempotency
Pass a unique idempotency key on retryable POST requests to safely retry failures without duplicate charges.
Antifraud-driven throttling
Antifraud rules (whitelists, blacklists, velocity) may block individual charges. These are not rate limits in the traditional sense but can manifest as repeated 402/422 responses.
Webhook retries
Endpoints must respond with 2xx within the timeout to acknowledge delivery. Repeated non-2xx responses trigger retries on an exponential schedule.
Localization header
Every request must include Accept-Language (es or en). Missing the header causes 400 errors that may look like throttling but are validation failures.