Skip to main content

BGC Laboral (Employment History)

The BGC Laboral process runs an automated query to obtain the candidate's official employment history (e.g., IMSS in Mexico), allowing you to verify contributed weeks, previous employers, and registered base salaries.

Entity Restriction

This process is exclusive to Individuals (PF) (individual candidates). It is not available for corporate or business records.

Registration Methods (Input Payloads)​

To initialize a candidate's employment process, two registration methods are supported in the input payload. Providing the Social Security Number (nss) is optional but highly recommended, since it speeds up the lookup in the official source.

This method registers the candidate using their national identifier (such as CURP in Mexico).

{
  "byNationalId": true,
  "nationalId": "CURP_PLACEHOLDER",
  "clientId": "CL_12345",
  "package": "PKG_LABORAL_01",
  "taxClassification": "PF",
  "nss": "12345678901" // Optional: Providing it speeds up the lookup in the official source
}

Response Architecture (Summary vs Extended)​

The API structures the returned employment information according to the level of detail requested through the detail query parameter:

  • Global Metrics (Summary View): By default, the API returns the candidate's overall summary in the detail node, which includes fields such as total_semanas_cotizadas, total_razones_sociales, total_empleos, average weeks, etc.
  • Detailed History (Extended View / ?detail=true): Enables the historia_laboral array inside the detail node. This array breaks down, in chronological order, each of the candidate's registered employer-employee relationships.
Data Source

Note on format: The internal fields of the detail object and historia_laboral are presented in Spanish and keep the official technical naming of the issuing social security institution (e.g., registro_patronal, salario_base_cotizacion). This guarantees the integrity, fidelity, and transparency of the raw data extracted from the government source.

Annotated Response Example​

The following are structured, fully anonymized examples that contrast the basic response with the extended one, using fictitious data.

This basic structure is returned by default (without passing ?detail=true), returning only the global metrics calculated for the candidate.

{
  "isSuccess": true,
  "statusCode": 200,
  "message": "Success",
  "data": {
    "processId": "zrQKr9R0ksg0QHMQ3Wo1",
    "processName": "BGC Laboral",
    "detail": {
      "nss": "12345678901",
      "fecha_emision_reporte": "2026-06-29",
      "total_semanas_cotizadas": "17", // Total weeks accumulated in the institutional employment record
      "total_razones_sociales": "2",
      "total_empleos": "2"
    },
    "status": "Finalizado",
    "result": "Proceso completo"
  }
}