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, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_minute and retries.

Limit state is signalled in the requestId response header, and 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 4 backoff/retry policies defined and response codes documented for throttled and serverBusy.

Tagged areas include Rate Limiting, Payments, and Mexico.

2 Limits Exhausted: HTTP 429 requestId
Method: generated, dated 2026-05-24.
Written by API Evangelist on 2026-05-24 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingPaymentsMexico

Limits

Per-merchant API request rate account
requests_per_minute · minute
undisclosed
Webhook delivery retries webhook
retries · 48h
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.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/conekta-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.