Skip to Content
Changelog12/11/2026 · TGSS contract change: tgss_actual and tgss_enviado in the response

TGSS contract change: tgss_actual and tgss_enviado in the response

12/11/2026

Affects PUT /api/v4/seg-social/contract-coeficiente (Contract change) and its MCP tool.

  • data.tgss_actual and data.tgss_enviado, with or without an error. tgss_actual is what TGSS had on the contract change screen before the change (starts with fecha_registro); tgss_enviado, what was sent (starts with fecha_cambio). Same readable keys in both, to compare them and see what caused a rejection. data.dni and data.nss are also included. A success without duplicates, which used to return an empty data, now has these keys.
  • The specific F.I.C. is no longer sent. Saltra sent the contract seniority date as the specific F.I.C., and with a total strike TGSS responded 5075* EN SIT. DE HUELGA TOTAL NO SE PUEDE CAMBIAR CARACTERISTICAS. TGSS now keeps the worker’s current one.
  • Strike registered at TGSS. If tgss_actual contains an inactivity type and the contract is in Saltra, it is stored on it from fecha_registro, even when TGSS rejects the change.
  • The IDC returns the inactivity type. GET /api/v4/seg-social/duplicate-idc?format=json (Contribution data) adds tgss_inactividad and tgss_ctp_huelga to data.parsed.contract when the IDC has them (for example, “HUELGA TOTAL” → 2). When syncing by IDC, that strike is stored on the Saltra contract from the start of the IDC period.
  • “Worker’s IDC data” moves to Queries as List worker IDCs. The endpoint (GET /api/v4/seg-social/idc-info-for-nss) does not change and the old URL redirects.

What to check in your integration: nothing mandatory. If you validate that data is empty on success, accept the new keys.

Last updated on