List retry attempts

GEThttps://api.veriko.mx/v1/validations/{id}/retry-attempts

List retry attempts

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

Returns every automatic retry made on a validation, in order. Each entry carries the dispatch, start, and finish timestamps, the verdict before and after the attempt, how long it took, and the error code if there was one. It serves to understand why a validation ended up where it did: the policy governing those attempts is in the retry policy.

Parameters
Parameter	In	Type	Required	Description
`id`*	path	`string (uuid)`	required	Validation UUID.

Request

cURLPython•JavaScript•PHP•

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

Python example — coming soon.

JavaScript example — coming soon.

PHP example — coming soon.

**Response 200**`RetryAttempt` — List of retry attempts in chronological order (ASC by attempt_number).
Field	Type	Description
`attempt_number`	`integer`	Sequence number of the attempt (1-based). e.g. `1`
`dispatched_at`	`string (date-time)`	ISO 8601 timestamp in UTC with explicit `Z` suffix. Example: `"2026-05-01T05:14:38Z"`. Every datetime field uses this shape. The descriptor at `meta.datetime` makes the contract runtime-assertable. e.g. `2026-05-01T05:14:38Z`
`started_at`	`string (date-time)`	ISO 8601 timestamp in UTC with explicit `Z` suffix. Example: `"2026-05-01T05:14:38Z"`. Every datetime field uses this shape. The descriptor at `meta.datetime` makes the contract runtime-assertable. e.g. `2026-05-01T05:14:38Z`
`finished_at`	`string (date-time)`	ISO 8601 timestamp in UTC with explicit `Z` suffix. Example: `"2026-05-01T05:14:38Z"`. Every datetime field uses this shape. The descriptor at `meta.datetime` makes the contract runtime-assertable. e.g. `2026-05-01T05:14:38Z`
`prev_banxico_status`	`string`	Banxico status of the validation immediately before this attempt (e.g. `not_found`). The verdicts are `valid`, `not_found`, `cep_unavailable`, `invalid`, and `error`. e.g. `not_found`
`new_banxico_status`	`string \| null`nullable	Banxico status after the attempt completed. `null` if the attempt did not receive a Banxico response (e.g. network failure). The verdicts are `valid`, `not_found`, `cep_unavailable`, `invalid`, and `error`. e.g. `valid`
`prev_status`	`string`	Validation status before the attempt. The states are `queued`, `processing`, `valid`, `not_found`, `cep_unavailable`, `invalid`, `failed`, and `error`. e.g. `not_found`
`new_status`	`string \| null`nullable	Validation status after the attempt. `null` if the attempt did not produce a state transition. The states are `queued`, `processing`, `valid`, `not_found`, `cep_unavailable`, `invalid`, `failed`, and `error`. e.g. `valid`
`processing_time_ms`	`integer \| null`nullable	Processing time for the attempt in milliseconds. `null` if the attempt did not complete. e.g. `1250`
`error_code`	`ValidationErrorCode \| null`	Error code if the attempt ended in failure. See `ValidationErrorCode` for possible values. `null` if the attempt completed without error. e.g. `network`
`proxy_pool_member`	`string \| null`nullable	Identifier of the proxy used for this attempt. Useful for diagnosing repeated failures on the same node. e.g. `proxy-03`

**Response status codes**`GET /v1/validations/{id}/retry-attempts`
Status	Class	Description	Body
200	`2xx`	List of retry attempts in chronological order (ASC by attempt_number).	No body
401	`4xx`	Authentication is required or the provided credentials are invalid.	`ErrorResponse`
403	`4xx`	Insufficient permissions.	`ErrorResponse`
404	`4xx`	Validation not found (`not_found`).	`ErrorResponse`
422	`4xx`	Invalid UUID in path (`invalid_uuid`).	`ErrorResponse`

**Errors from `GET /v1/validations/{id}/retry-attempts`**
Status	Code	Example
401	`unauthorized`	Invalid or missing authentication credentials. Envelope meta.request_id `c4d5e6f7a8b9`
403	`forbidden`	You do not have permission to access this resource. Envelope meta.request_id `d5e6f7a8b9c0`