Skip to main content

IMSS - Employment Information Request

Description​

Creates an IMSS employment information verification request using the person's CURP. The response returns a request identifier that must be used to retrieve the result.

Asynchronous Flow

This API uses an asynchronous two-step process:

  1. Create the request — returns a requestId and PENDING status.
  2. Retrieve the result — use the ticket to poll the status endpoint until the process finishes.

Step 1 — Create the request​

HTTP method POST​

Endpoint​

https://api.msla-id.com/experience-idv-socialsecurity-api-v1/api/idv-govcheck/v1/mx-identity/imss-ticket
[SANDBOX Environment]

For testing purposes, use the base domain: apidev.msla-id.com

info

Before proceeding, make sure you have your JWT token. If you do not, check the login documentation.

Request header parameters​

NAMEREQUIREDTYPEDESCRIPTION
Authorization✅stringBearer JWT token.
Content-Type✅stringapplication/json.

Request body parameters​

{
"curp": "GOCS031114MMCLRLA0"
}
NAMEREQUIREDTYPEDESCRIPTION
curp✅stringMexican CURP.

Status code responses​

CodeDescription
200Request created successfully.
400Bad request — IDV- INS1001, IDV-INS1002, DOM-3001
401Unauthorized
403Forbidden — IDV-1004
500Internal server error — IDV-1008
504Gateway timeout — IDV-1100

The full documentation error codes can be found here.

Response 200 status code​

{
"traceId": "35f34a6de6cf095c",
"timestamp": "2026-08-11 10:08:07",
"data": {
"requestId": "56ebda5f-d2c4-4d3e-b4ef-03a0a48300a7",
"status": "PENDING"
}
}

Response 400 status code — Bad Request​

{
"traceId": "05c5e114fd71deb7",
"timestamp": "2026-08-13 17:26:33",
"code": "IDV- INS1001",
"message": "A CURP is required in the request."
}

Note: This error occurs when the request does not include the CURP. Please provide it.

{
"traceId": "89a3649dc08cc011",
"timestamp": "2026-08-13 17:28:22",
"code": "IDV-INS1002",
"message": "The provided CURP is invalid."
}

Note: This error occurs when the CURP provided is invalid. Verify that the value is correct.

Response 400 status code​

{
"traceId": "7c6832744d1658ab",
"timestamp": "2026-08-11 16:48:27",
"code": "DOM-3001",
"message": "Error in the call to the supplier",
"data": null
}

This error can occur when there is a problem with the supplier connection or the request is incorrectly formatted.

Response 500 status code​

{
"traceId": "86c6eda02b615604",
"timestamp": "2026-08-11 15:44:32",
"code": "IDV-1008",
"message": "Error in the source of origin, please contact an administrator!"
}

Response 403 status code​

{
"traceId": "43a20f33d4e8730d",
"timestamp": "yyyy-mm-dd HH:MM:SS",
"code": "IDV-1004",
"message": "Forbidden",
"data": null
}

Response 504 status code​

{
"traceId": "86c6eda02b615604",
"timestamp": "2026-08-11 15:44:32",
"code": "IDV-1100",
"message": "Gateway Timeout",
"data": null
}