Changelog
Back to All

🏛️ ISSSTE Retired Employment Status & Async Bulk Operations

about 1 month ago by Assad Aboultaif

🏛️ ISSSTE Retired Employment Status

Profile and employment endpoints now support a retired employment status, reflecting pensioners from ISSSTE (Instituto de Seguridad y Servicios Sociales de los Trabajadores del Estado).

🆕 What's New

GET /profile/identifier — New retired value in employment_status enum:

  • employed — Currently employed
  • unemployed — Not currently employed
  • retired — Receiving pension (e.g., ISSSTE pensioners)
  • unknown — Status could not be determined

GET /employments/identifier — New example scenario showing ISSSTE retiree employment history with pension records (I.S.S.S.T.E. PENSIONISTAS DIRECTOS) alongside prior government and private-sector employment.

💡 What This Means for You

  • No breaking changes — existing integrations continue to work as before.
  • You can now distinguish retirees from unemployed individuals when processing profile data.
  • Employment history for retirees will typically show a pension record with no end_date, preceded by their prior employment history.

⚡ Async Bulk Operations

POST /verifications/bulk and POST /consents/bulk now return an immediate queued response instead of waiting for synchronous processing.

🆕 Updated Behavior

Before (207 Multi-Status) — Response waited for synchronous processing:

{
  "bulk_id": "cd9441c8-6eab-4343-be54-329dc0cad139",
  "total": 2,
  "successful": 2,
  "failed": 0,
  "results": [
    {
      "id": "019982f6-80d5-7b3f-8339-d26dcc537b9b",
      "identifier": "ABCD123456DEFGHI01",
      "status": "successful",
      "verification_status": "in_progress",
      "created_at": "2025-09-25T22:20:16.981694700Z",
      "consent_id": "019982f6-7685-7805-bb70-0ab2dc3ab833"
    }
  ]
}

After (202 Accepted) — Immediate queued response:

{
  "id": "ec412814-09ed-4e3a-99d0-4e4d3277b07e",
  "status": "pending",
  "total_items": 2,
  "message": "Batch verification creation queued successfully."
}

Use the returned id to poll status via GET /verifications/bulk/bulk_id.

⚠️ Breaking Change

  • Previous behavior: Both bulk endpoints returned 207 Multi-Status with individual results inline.
  • New behavior: Both return 202 Accepted with a job id, status, total_items, and message. Individual results are available by polling the bulk status endpoint.

💡 What This Means for You

  • Faster responses — bulk requests are queued immediately, no waiting for processing.
  • Poll for results — use the returned id to check progress via GET /verifications/bulk/{bulk_id}.
  • Update your integrations — if you were parsing the 207 response with inline results, you'll need to switch to the async polling pattern.