GEThttps://api.veriko.mx/v1/status/banxico

Get the Banxico service status (public view)

Audience: public
Auth: API key

Returns the current operational status of the Banxico validation service, derived from periodic health checks.

The status can be:

operational: All checks pass and latency is normal.
degraded: Partial issues — high latency or intermittent errors.
down: The service is unreachable for now.
unknown: There is no current health data: no check has run yet, or the last one is more than three times check_interval_seconds old because the automated check stopped running. In that case last_verified_at keeps the date of that last check.

The response is cached 60 seconds on the client with Cache-Control, and that window is set at deploy time. Any authenticated user can query it, and no specific permission is required.

Request

cURLPython•JavaScript•PHP•

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

Python example — coming soon.

JavaScript example — coming soon.

PHP example — coming soon.

**Response 200**`BanxicoPublicStatusResponse` — Current Banxico validation service status.
Field	Type	Description
`data`	`object`	Main response payload. Shape varies by endpoint (object, array, or JSON:API envelope with `type`, `id`, `attributes`).
`type`*	`string`	JSON:API resource type. Always `banxico_status`. e.g. `banxico_status`
`id`*	`string`	Fixed `current` identifier (the current status entry). e.g. `current`
`attributes`*	`object`	Public status of the Banxico validation service, as returned by `GET /v1/status/banxico`. It shows the current operational status and a human-readable explanation.
`status`*	`string`	Aggregated service status — `operational`: all checks pass and latency is normal; `degraded`: partial issues (high latency or intermittent errors); `down`: service unreachable; `unknown`: no current health data, because no check has run yet or because the last one is more than three times `check_interval_seconds` old (the automated check stopped running). e.g. `operational`
`status_label`*	`string`	Human-readable status label, resolved to the request locale. e.g. `Operativo`
`message`*	`string`	Short explanation of the current service status, resolved to the request locale. e.g. `El servicio de verificación está operando normalmente.`
`last_verified_at`*	`TimestampUTC \| null`	Timestamp of the last health check executed. `null` when no check has been run yet. When `status` is `unknown` because the last check is too old, it keeps that check's date: it says since when there is no data. e.g. `2026-04-11T15:30:00Z`
`estimated_recovery_at`	`TimestampUTC \| null`	Estimated service recovery time. Only set for a specific kind of transient degradation with a known recovery window; `null` in every other case, including other kinds of `degraded`. e.g. `null`
`check_interval_seconds`	`integer`	Cadence (in seconds) of the automated health check that feeds this status. It is read live from the configured schedule, so a change takes effect without a deploy; when no cadence is configured, it is `300`. e.g. `300`
`meta`	`object`	Response metadata including API version, route prefix, unique request identifier, and the server timestamp in UTC.
`version`	`string`	API version that processed the request. e.g. `1.47.0`
`api_version`	`string`	API route prefix version (e.g. `v1`). e.g. `v1`
`request_id`	`string`	Unique request identifier (hex). e.g. `a1b2c3d4e5f66f5e4d3c2b1a`
`datetime`	`object`	Companion descriptor present in the `meta` block of every response (and in the `meta` of outgoing webhook bodies). Lets clients assert the timezone contract without re-reading the spec. e.g. `{"timezone":"UTC","format":"ISO 8601"}`
`timezone`*	`string`	Always `UTC`: The canonical timezone for every datetime field in the body. e.g. `UTC`
`format`*	`string`	Always `ISO 8601`: Explicit `Z` suffix on every datetime. e.g. `ISO 8601`
`links`	`object`	Pagination or related links, present only when the endpoint returns a paginated collection.

**Response status codes**`GET /v1/status/banxico`
Status	Class	Description	Body
200	`2xx`	Current Banxico validation service status.	`BanxicoPublicStatusResponse`
401	`4xx`	Authentication is required or the provided credentials are invalid.	`ErrorResponse`

**Response headers**`200`
Header	Type	Description
`Cache-Control`	`string`	Public-view cache TTL (configurable; defaults to 60 s).
`Vary`	`string`	Origin-based variation marker (CORS).

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