Create preference with the Mercado Pago API

Creates a payment preference and returns it with id and init_point, the Checkout Pro link where the buyer pays by Pix, card, boleto or Mercado Pago balance. Each item needs id, title, quantity and unit_price. Share init_point with the buyer.

Identifier
mercado_pago_create_preference

The request

POST https://connect.reportei.com/api/tools/mercado_pago_create_preference/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "items": []
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
itemsarrayYesProducts or services of the payment. The total is the sum of quantity times unit_price.
payerobjectNoBuyer data that fills in the checkout.
payment_methodsobjectNoPayment options of the checkout.
back_urlsobjectNoPages of the seller's site the buyer returns to after the checkout.
auto_returnstringNoapproved sends the buyer to back_urls.success right after an approved card payment. Needs back_urls.success.Values: approved, all
statement_descriptorstringNoText on the buyer's card statement, up to 13 characters.
external_referencestringNoYour own code for this sale. Its payments carry it, so Search payments finds them by it.
expiresbooleanNotrue makes the link valid only between expiration_date_from and expiration_date_to.
expiration_date_fromstringNoStart of the validity, like 2026-11-01T00:00:00.000-03:00.
expiration_date_tostringNoEnd of the validity, in the same format as expiration_date_from.
metadataobjectNoFree key-value data saved with the preference.

Supported connections

Your customer connects their Mercado Pago account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/mercado_pago_create_preference. It becomes your agent's tool definition with no conversion.

Other Mercado Pago tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.