ISSSTE Record
Credits: 1 per call.
Retrieves a government worker’s full ISSSTE record by CURP — personal data, affiliation, pension regime, positions, contribution history, address, assigned clinic, and the official PDF (always included as base64 in data.files[] (kind document)).
A retrieved record returns type: SUCCESS for an active worker. PENSIONER, SCHOLAR, INACTIVE, and DECEASED flag KYC-material standings; when more than one applies, precedence is DECEASED > PENSIONER/SCHOLAR > INACTIVE. The raw affiliation status and beneficiary type are always in data.affiliation, so new statuses ISSSTE may report never break the contract. CURP_NOT_FOUND when the CURP has no ISSSTE record. Dates are ISO YYYY-MM-DD; monetary amounts are strings (MXN).
Field presence: every field is always present (stable contract) — absent values are null (objects/scalars, including empty source strings normalized to null) or [] (arrays), never omitted. Examples: pensions and family are [] when the worker has none; terminationDate and a history row’s endDate are null while ongoing; binary assets in data.files[] follow array semantics — only assets actually produced are listed (absent ones omitted, not null). Unmigrated placeholder values from ISSSTE (e.g. address POR ACTUALIZAR, clinic FAVOR DE ATENDER A ESTE TRABAJADOR / clave 0409999, state ENTIDAD DESCONOCIDA) are normalized to null (data not yet migrated). ISSSTE only exposes records for titulares (TRABAJADOR/PENSIONISTA/BECARIO); a CURP that is only a dependant (not a titular) returns CURP_NOT_FOUND. To retrieve a dependant, query the titular CURP and match data.family[] by the dependant CURP. beneficiaryType is derived authoritatively from the record (a DIRECT pension means PENSIONISTA even if the document labels them TRABAJADOR); each pension carries a derived category (DIRECT/SURVIVOR/INSURANCE/DISABILITY).
Autorizaciones
Cuerpo
CURP of the government worker whose ISSSTE record is requested.
"GOTM850312MDFMRX05"
Respuesta
ISSSTE record result (Strict Envelope Pattern).
High-level outcome. OK means the request was successfully processed (regardless of business result). ERROR means the request was rejected or could not be processed.
OK, ERROR Stable result type code. Includes generic codes (SUCCESS, INVALID_REQUEST, UNAUTHORIZED, SERVICE_UNAVAILABLE, INTERNAL_ERROR, RATE_LIMIT_EXCEEDED) plus endpoint-specific result codes — see this endpoint's response examples.
Human-readable summary of the result. Always in English (per Language Conventions in the API overview).
Unique identifier of this request, generated by the API Gateway. Propagated end-to-end for traceability.
ISO 8601 datetime with Mexico City offset (-06:00). Always set by the API Gateway when the response leaves the system.
Whether this request will be charged against the client's plan. Typically true for successful business results and false for validation errors or system errors that prevented processing.
Full ISSSTE record for a government worker. Present only when type is SUCCESS.
Per-field error details. Present only on INVALID_REQUEST responses.