Search payments with the Mercado Pago API

Searches the payments the account received in the last 12 months; without dates, the ones created in the last 3 months. The response has results and paging with total, limit and offset: raise offset by limit to read the next page.

Identifier
mercado_pago_search_payments

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "sort": "date_approved"
  }
}

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
sortstringNoField that orders the results.Values: date_approved, date_created, date_last_updated, id, money_release_date
criteriastringNoDirection of sort: asc or desc.Values: asc, desc
rangestringNoDate field that begin_date and end_date filter. The default is date_created.Values: date_created, date_last_updated, date_approved, money_release_date
begin_datestringNoStart of the period: an ISO 8601 date, like 2026-09-01T00:00:00.000-03:00, or a relative one, like NOW-30DAYS or NOW-1MONTH. The default is NOW-3MONTHS.
end_datestringNoEnd of the period, in the same formats as begin_date. The default is NOW.
external_referencestringNoOnly the payments with this external_reference, the seller's own code set on the preference or the payment.
limitintegerNoPayments per page.
offsetintegerNoPayments to skip, for paging.

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_search_payments. 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.