Mercado Pago · Mercado Libre
Keep Mercado Pago · Mercado Libre in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
25 ways to read, 2 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Mercado Pago · Mercado Libre, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create Checkout Pro linkApproval by rule
- List release reportsRead
Example flow
- Mercado Pago · Mercado Libre · List release reportsDone
- Mercado Pago · Mercado Libre · Create Checkout Pro linkNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Mercado Pago · Mercado Libre.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Mercado Pago · Mercado Libre
- Mercado Pago · Mercado Libre's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Mercado Pago test account before you go live.
For developers
Technical detail
Mercado Pago: payments, refunds, merchant orders, Checkout Pro links, customers and cards, chargebacks, subscriptions and plans, stores, POS and reports.
Mercado Pago API docs- Source actions
- 25
- Destination actions
- 2
- Data types
- 14
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account1
- Get accountSource
Read the authorised account's user ID, nickname and site (needed for stores).
Chargebacks2
- Get chargebackSource
Read one Mercado Pago chargeback by ID.
- Search chargebacksSource
Read chargebacks, optionally for one payment.
Customer cards2
- Get customer cardSource
Read one Mercado Pago customer card by ID.
- List customer cardsSource
Read a customer's saved cards: brand, last four digits and expiry only.
Customers2
- Get customerSource
Read one Mercado Pago customer by ID.
- List customersSource
Read saved customers (offset paging, without email filters).
Merchant orders2
- Get merchant orderSource
Read one Mercado Pago merchant order by ID.
- Search merchant ordersSource
Read merchant orders that group Checkout Pro payments and shipments.
Payment refunds2
- Get payment refundSource
Read one Mercado Pago payment refund by ID.
- List payment refundsSource
Read the refunds of one payment; does not create refunds.
Payments2
- Get paymentSource
Read one Mercado Pago payment by ID.
- Search paymentsSourceIncremental
Read existing merchant payments and provider status.
Pos2
- Get point of saleSource
Read one Mercado Pago point of sale by ID.
- List points of saleSource
Read points of sale (QR cash registers), optionally for one store.
Preapproval plans2
- Get subscription planSource
Read one Mercado Pago subscription plan by ID.
- Search subscription plansSource
Read subscription plans (preapproval plans).
Preapprovals2
- Get subscriptionSource
Read one Mercado Pago subscription by ID.
- Search subscriptionsSource
Read subscriptions (preapprovals) with their charge summary.
Preferences4
- Create Checkout Pro linkDestinationProvider duplicate protectionApproval before production
Create a Checkout Pro preference and its payment link. No money moves until the buyer pays.
- Get preferenceSource
Read one Mercado Pago preference by ID.
- Search Checkout Pro preferencesSource
Read Checkout Pro payment links (preferences).
- Update Checkout Pro linkDestinationProvider duplicate protectionApproval before production
Change a preference's items, references, return URLs or expiry.
Release reports1
- List release reportsSource
Read generated release reports of funds released to the account balance.
Settlement reports1
- List settlement reportsSource
Read generated settlement (account money) reports for reconciliation.
Stores2
- Get storeSource
Read one Mercado Pago store by ID.
- List storesSource
Read the account's physical stores used for QR and Point payments.
Access and limits
- Authentication
- Mercado Pago merchant access token
- Plans and access
- A Mercado Pago seller account with an application and its production or test access token (APP_USR-...). Each country site (Brazil, Argentina, Mexico, ...) uses its own account; reports and stores need the collector user ID.
- Test environment
- Use test users and the test access token of your application.
- Rate limits
- Mercado Pago does not publish fixed limits; HTTP 429 is honoured with bounded retries.
- Pagination
- Search endpoints use offset and limit with paging.total (or total for preferences and merchant orders); POS search allows at most 30 per page.
- Provider events
- Mercado Pago sends payment, merchant order, subscription and chargeback notifications to the URL configured on the application or preference. Flows can start the moment something happens: when a payment is created; when a payment's status changes.
Before you build a flow
- Intentional exclusions: creating, capturing, cancelling or refunding payments; advanced payments and disbursements; orders API actions; creating or cancelling subscriptions and plans; customer and card creation or removal; chargeback documentation; creating, updating or deleting stores and POS; generating or downloading reports.
- Customer search by email is not offered because Mercado Pago takes the email in the URL; payer emails and identifications are never mapped.
- Card BINs (first six digits) and cardholder names are not mapped.
- An account balance endpoint is not part of Mercado Pago's current public reference, so balances come from the settlement and release reports.
Developer reference
- Create the Mercado Pago credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Mercado Pago · Mercado Libre, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/mercado-pago and the Connections API.