GEThttps://api.veriko.mx/v1/validations

List validations

Audience: public
Auth: API key
Permission: validations:read

Returns the paginated validation history of the authenticated account.

The filters combine with each other:

status accepts one status, or several separated by commas.
with_deleted distinguishes active records from withdrawn ones.
The rest narrow by mode, date, content, bank, amount, origin, reference of your own (client_ref) and retry cycle.

The shape of the response is described in pagination.

For the complete record of a validation, with the detailed state of its retries, there is GET /v1/validations/{id}.

Parameters
Parameter	In	Type	Required	Description
`amount_max`	query	`number (float)`	optional	Inclusive maximum amount, as a number. Same formatting-tolerance and error rules as `amount_min`. Applied independently of `amount_min`. e.g. `50000`
`amount_min`	query	`number (float)`	optional	Inclusive minimum amount, as a number. The server also tolerates sending it as text with a thousands separator or a currency symbol ("1,000.50", "$500") and normalizes it with the same algorithm used across the platform, but the contract is a number: a typed client should send it that way. A non-empty value that isn't recognized as a number returns HTTP status `422` with `invalid_filter`, instead of being silently ignored. Applied independently of `amount_max`. e.g. `1000.5`
`bank`	query	`string`	optional	SPEI code of the sending or receiving bank in the original request. Values outside 1 to 5 digits are ignored; sending it as a list (`bank[]=`) returns HTTP status `422` with `invalid_filter`. e.g. `012`
`banks`	query	`string`	optional	Comma-separated SPEI codes (up to 50); returns the validations whose sending or receiving bank is any of them. If an element does not have 1 to 5 digits, the response is HTTP status `422` with `invalid_filter`. Combines with `bank`: if you send both, both must hold. e.g. `40012,40014,40072`
`batch_id`	query	`integer`	optional	Identifier of the import job that generated the validations. Sending it as a list (`batch_id[]=`) returns HTTP status `422` with `invalid_filter` instead of being ignored. e.g. `42`
`client_ref`	query	`string`	optional	Exact match with the `client_ref` sent when validating. It distinguishes case, accents, and inner spaces. An empty value, or one that does not meet the `client_ref` rules, returns an HTTP status `422` (with `invalid_filter` in the body). e.g. `orden-4812`
`from`	query	`string (date)`	optional	Inclusive start date, applied to the validation creation date. Sending it as a list (`from[]=`) returns HTTP status `422` with `invalid_filter`. e.g. `2025-01-01`
`page`	query	`integer`	optional	Requested page; values below `1` are adjusted to `1`. Default: `1` e.g. `1`
`per_page`	query	`integer`	optional	Items per page; adjusted to the `1` to `50` range. Default: `10` e.g. `10`
`playground`	query	`string`	optional	Keeps only playground validations. The only accepted value is `1`; any other value returns HTTP status `422`. e.g. `1`
`retry_state`	query	`string`	optional	Retry cycle state: `pending`, `resolved`, `exhausted`, or `cancelled`. Any other value returns HTTP status `422` with `invalid_filter`. e.g. `pending`
`search`	query	`string`	optional	Case-insensitive text search over the submitted, normalized, and Banxico response data. `%` and `_` are treated as literal characters, and the 100-character limit is counted per character (not per byte), so an accented letter is never split in half. If the text, once spaces and hyphens are removed, is made up only of digits, that separator-free form is also matched against the beneficiary account. e.g. `scotiabank`
`status`	query	`string`	optional	Lifecycle state. Accepts one value or a comma-separated list: `queued`, `processing`, `valid`, `not_found`, `cep_unavailable`, `invalid`, `returned`, `failed`, or `error`. Unsupported values are ignored. e.g. `valid`
`to`	query	`string (date)`	optional	Inclusive end date, applied to the validation creation date. Sending it as a list (`to[]=`) returns HTTP status `422` with `invalid_filter`. e.g. `2025-03-31`
`type`	query	`string`	optional	Mode: `direct` for manual validation or `ocr` for image-based validation. e.g. `direct`
`with_deleted`	query	`string`	optional	Scope for withdrawn records: omitted includes active and withdrawn records; `0` keeps active records only and `1`, withdrawn records only. e.g. `0`

Request

cURLPython•JavaScript•PHP•

curl -X GET 'https://api.veriko.mx/v1/validations' \
  -H 'Authorization: Bearer veriko_••••'

Python example — coming soon.

JavaScript example — coming soon.

PHP example — coming soon.

**Response 200**`PublicValidationListItem` — Paginated list of validations with pagination metadata.
Field	Type	Description
`type`*	`string`	Resource type. It is a fixed value per resource and does not vary between responses; it tells resources apart when a collection mixes several. e.g. `validation`
`id`*	`string (uuid)`	Resource identifier, unique within its `type`. It always travels as a string, even when it originates from an auto-increment column.
`attributes`*	`object`	Data shown in the validation history.
`bank_name`	`string`	Counterparty bank name. It first uses the stored `receptor_name` or `emisor_name`; if absent, it tries to resolve the receiver or sender code. If resolution also fails, it returns the stored value when it is not a numeric code, or `Unidentified bank` (in Spanish, `Banco no identificado`).
`bank_code`	`string \| null`nullable	Canonical Banxico key (3-5 digits) of the counterparty bank, resolved by the domain authority. `null` when the bank could not be resolved. Additive to `bank_name`: it is used to resolve resources/avatars by key, never by the visible name.
`beneficiary_label`	`string \| null`nullable	Registered beneficiary label, when available.
`amount`	`number \| null`nullable	Transfer amount in Mexican pesos (MXN).
`tracking_key`	`string`	Identifier assigned by the sending bank of the transfer (tracking key).
`referencia_numerica`	`string`	Numeric series of up to 7 digits that identifies the transfer. It is not unique and may repeat.
`beneficiary_account`	`string`	CLABE, card, or mobile number that received the transfer.
`status`	`string`	Lifecycle state — `queued`: Awaiting processing; `processing`: In progress; `valid`: The CEP was found and matches; `not_found`: Banxico cannot find the operation; `cep_unavailable`: Banxico recognizes the transaction but the CEP is not available; `invalid`: Banxico did not return a recognizable verdict; `returned`: the transfer was settled and later returned; `failed`: The validation stopped because of a problem in the data sent; `error`: The validation stopped because of a service failure.
`banxico_status`	`string`	Verdict reported by Banxico.
`validation_type`	`string`	Validation mode — `direct`: Manual entry of the fields; `ocr`: Reading of the receipt image.
`is_playground`	`boolean`	`true` when the validation belongs to the playground.
`created_at`	`string (date-time)`	ISO 8601 timestamp in UTC with an explicit `Z` suffix; for example, `"2026-05-01T05:14:38Z"`. The `_at`, `_end`, `_start`, and `_date` fields follow this format. `meta.datetime` describes the same contract in the response. e.g. `2026-05-01T05:14:38Z`
`deleted_at`	`TimestampUTC \| null`	History withdrawal date in ISO 8601 UTC.
`purged_at`	`object`	Date and time, in ISO 8601 UTC, when the validation was purged. It only appears on a purged validation, which is left as a tombstone with its verdict, its dates, and its amount.
`retry_state`	`object`	Summary retry cycle state with configuration represented as `null`.
`enabled`	`boolean`	`true` when the validation has retries configured, even if its cycle has already ended (`terminal_state`). e.g. `true`
`max_retries`	`integer \| null`nullable	Always `null` in the summary shape. e.g. `null`
`interval_seconds`	`integer \| null`nullable	Always `null` in the summary shape. e.g. `null`
`outcomes`	`array \| null`nullable	Always `null` in the summary shape. e.g. `null`
`attempts_completed`	`integer`	Number of retries completed so far. e.g. `2`
`next_attempt_at`	`TimestampUTC \| null`	Date of the next retry; `null` when none is scheduled.
`resolved_at`	`TimestampUTC \| null`	Date when a retry produced `valid`; `null` until that occurs.
`exhausted_at`	`TimestampUTC \| null`	Date when attempts were exhausted; `null` until that occurs.
`cancelled_at`	`TimestampUTC \| null`	Cycle cancellation date; `null` until that occurs.
`terminal_state`	`string \| null`nullable	Cycle state: `pending`, `resolved`, `exhausted`, or `cancelled`. It is `null` when the validation has no retry cycle. e.g. `pending`
`client_ref`	`string`	Reference of your own sent when validating (`client_ref`), returned as sent. It only appears when the request included it. e.g. `orden-4812`

**Response status codes**`GET /v1/validations`
Status	Class	Description	Body
200	`2xx`	Paginated list of validations with pagination metadata.	`PublicValidationListItem`
401	`4xx`	Authentication is required or the provided credentials are invalid.	`ErrorResponse`
422	`4xx`	A filter could not be applied (code `invalid_filter`): unsupported value in `retry_state`, `playground`, or `amount_min`/`amount_max` with an unrecognized format; or the wrong type in `from`, `to`, `search`, `bank`, or `batch_id` (for example, sent as a list `from[]=`).	`ErrorResponse`

**Errors from `GET /v1/validations`**
Status	Code	Example
401	`unauthorized`	Invalid or missing authentication credentials. Envelope meta.request_id `c4d5e6f7a8b99b8a7f6e5d4c`