Machine-readable, standards-compliant OpenAPI 3.1 specification for all MercadoPago API endpoints across 7 countries in Latin America: Argentina, Brazil, Mexico, Chile, Colombia, Peru, and Uruguay.
| File | Description |
|---|---|
spec3.yaml |
Public spec — 136 endpoints, 31 tags, 65 schemas, fully self-contained |
spec3.json |
JSON twin of spec3.yaml (generated, never edited manually) |
spec3.sdk.yaml |
SDK variant — same as spec3.yaml plus x-mp-sdk-coverage per operation |
spec3.sdk.json |
JSON twin of spec3.sdk.yaml |
fixtures3.yaml |
Sample response objects per resource, used by mock servers |
fixtures3.json |
JSON twin of fixtures3.yaml |
schemas/ contains human-editable source fragments merged into spec3.yaml by the build pipeline.
Never $ref them from spec3.yaml directly — the spec must remain self-contained.
| Section | Product | API / Tag | Endpoints |
|---|---|---|---|
| Authentication | OAuth 2.0 | OAuth | 1 |
| Online Payments | Checkout Pro | Preferences API | 5 |
| Online Payments | Checkout Pro | Merchant Orders | 3 |
| Online Payments | Checkout API / Checkout Transparente (Orders API) | Orders | 14 |
| Online Payments | Payments API (legacy — use Orders API for new integrations) | Payments | 4 |
| Customers & Cards | — | Customers, Cards, Addresses, Card Tokens | 19 |
| Payment Methods | — | Payment Methods, Identification Types | 3 |
| Cancellations & Refunds | — | Cancellations & Refunds, Chargebacks | 7 |
| Subscriptions | — | Subscriptions, Plans, Invoices | 11 |
| Wallet Connect | Wallet Connect (Assisted Portfolio — requires direct engagement with the Mercado Pago team) | Wallet Connect | 4 |
| In-Person — Point | Mercado Pago Point | Stores, POS, Terminals, Point Orders, Point Deprecated | 20 |
| In-Person — QR | QR Code | QR Orders, QR Integrator, QR Deprecated | 13 |
| Post-Sale | — | Claims, Claim Messages, Claim Resolutions, Claim Shipping | 14 |
| Reports | — | Releases Report, Settlements Report | 20 |
| Payouts | — | Payouts | 5 |
Brazil (MLB): "Checkout API" is officially called Checkout Transparente in Brazil. Both names refer to the same Orders API integration.
7 endpoints are marked deprecated: true with x-mp-migration-guide pointers to modern equivalents.
Not all products are available in every country. Use the table below before building an integration:
| Product | MLA | MLB | MLM | MLC | MCO | MPE | MLU |
|---|---|---|---|---|---|---|---|
| Checkout Pro (Preferences API) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Checkout API / Checkout Transparente (Orders API) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Payments API (legacy) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Subscriptions | ✓ | ✓ | ✓ | — | — | — | — |
| Wallet Connect (Assisted Portfolio) | ✓ | ✓ | ✓ | — | — | — | — |
| Mercado Pago Point (Terminals) | ✓ | ✓ | ✓ | — | — | — | — |
| QR Code | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Claims | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Reports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Payouts | ✓ | ✓ | ✓ | ✓ | — | — | — |
Availability is annotated per-endpoint via the
x-mp-sitesextension. Per-country specs live inby-site/<site_id>/spec3.yaml.
Source: official SDKs — php, nodejs, java, python, ruby, dotnet, go
| Coverage | Count |
|---|---|
| All 7 SDKs | 38 |
| Partial SDK support | 21 |
| Spec-only (no SDK yet) | 77 |
Pre-merged per-site specs filtered to only the endpoints applicable to each country:
| Site | Country | Currency | Endpoints |
|---|---|---|---|
| MLA | Argentina | ARS | 134 |
| MLB | Brazil | BRL | 133 |
| MLM | Mexico | MXN | 133 |
| MLC | Chile | CLP | 117 |
| MCO | Colombia | COP | 114 |
| MPE | Peru | PEN | 114 |
| MLU | Uruguay | UYU | 114 |
- Open Postman → Import → Link
- Paste the raw URL of
spec3.yaml - Postman generates a full collection with all 136 endpoints and pre-filled examples
docker run --rm -p 4010:4010 \
-v $(pwd):/tmp/spec \
stoplight/prism mock /tmp/spec/spec3.yamlThen call any endpoint against http://localhost:4010 — Prism serves responses from fixtures3.yaml.
npx @redocly/cli preview-docs spec3.yamlMercadoPago uses three authentication patterns:
| Pattern | OpenAPI scheme | Used for |
|---|---|---|
| Bearer Access Token | bearerAuth |
All server-side endpoints |
| Public Key | publicKey |
Client-side card tokenization via MercadoPago.js only |
| OAuth 2.0 | mercadopagoOAuth |
Marketplace on-behalf-of, Wallet Connect |
Critical rules:
- Tokens go in
Authorization: Bearer <token>header only — never as?access_token=URL parameter APP_USR-xxxfor production- Public key is not an access token — using it server-side is a security misconfiguration
⚠️ MercadoPago uses decimal amounts, not integer cents.
| Currency | Decimals | Correct | Wrong |
|---|---|---|---|
| BRL, ARS, MXN, COP, PEN, UYU | 2 | 100.50 |
10050 |
| CLP | 0 | 10000 |
10000.00 |
MercadoPago Secure Fields and MercadoPago.js capture raw card data (PAN, CVV) directly in MP's infrastructure — your server only receives a single-use token. Integrations using this approach are out of PCI DSS scope for card data storage.
Endpoints with x-mp-pci-scope: true handle card tokenization.
| Country | site_id | Currency | Key local payment methods |
|---|---|---|---|
| Argentina | MLA | ARS | Rapipago, Pago Fácil, Amex, Naranja |
| Brazil | MLB | BRL | Pix, Boleto Bancário, Elo, Hipercard |
| Mexico | MLM | MXN | OXXO, SPEI, Citibanamex |
| Chile | MLC | CLP | Khipu, RedCompra |
| Colombia | MCO | COP | PSE, Efecty, Baloto |
| Peru | MPE | PEN | PagoEfectivo |
| Uruguay | MLU | UYU | OCA, Redpagos, Abitab |
The x-mp-sites extension on each endpoint and tag lists the applicable site_id codes.
Country-specific examples and local payment method details are in overlays/<site_id>.yaml.
| Extension | Where | Description |
|---|---|---|
x-mp-sites |
tag, endpoint | Applicable site_id codes |
x-mp-release-phase |
endpoint | legacy for deprecated integration patterns |
x-mp-pci-scope |
endpoint | true for card tokenization endpoints |
x-mp-migration-guide |
endpoint | Link to recommended modern equivalent |
x-mp-sdk-coverage |
endpoint (sdk spec only) | Which SDKs implement this endpoint |
openapi/
├── spec3.yaml # self-contained public spec (136 endpoints, 31 tags, 65 schemas)
├── spec3.json # JSON twin (generated)
├── spec3.sdk.yaml # SDK variant with x-mp-sdk-coverage per operation
├── spec3.sdk.json # JSON twin (generated)
├── fixtures3.yaml # sample response objects (12 resources)
├── fixtures3.json # JSON twin (generated)
├── schemas/ # human-editable source fragments (10 files)
├── overlays/ # OAL 1.0 country-specific additions (7 countries)
├── by-site/ # pre-merged per-site specs (MLA, MLB, MLM, MLC, MCO, MPE, MLU)
└── preview/ # pre-GA endpoints
See CONTRIBUTING.md for how to report missing or incorrect endpoints, run validation locally, and submit a pull request.
MercadoPago Developer Experience · Apache 2.0