TGSS contract change: strike rules and end of strike in the history
26/10/2026
Affects the contract change (PUT /api/v4/seg-social/contract-coeficiente) and its MCP tool tgss_update_contract_coeficiente.
The strike CTP belongs only to partial strikes: new 422s
Behaviour change. Before sending anything to TGSS, tgss_ctp_huelga is checked against tgss_inactividad, and the API responds 422 without submitting (the MCP tool returns an error with the same text):
- Full strike (
2) with a strike CTP: no part of the working day is worked in a full strike, so a strike CTP does not apply. - Partial strike (
3) without a strike CTP: the strike CTP (the coefficient of the worked part of the day) is required. - Strike CTP
0or000, with any inactivity: if nothing is worked, it is a full strike (type2without CTP). Previously a0was treated as empty.
With the other inactivity types (ERE/ERTE) the strike CTP is not validated: TGSS still decides. Details and messages in Strike rules.
The end of the strike is kept in the history
Until now this endpoint only submitted to TGSS and saved nothing on the Saltra contract. Now, if the change succeeds and the worker has their contract in Saltra (looked up by ccc among your company’s accounts or those of the companies you manage), the change is saved on it with the change date (startDate), as from the web.
The ATR45 has no end date: a strike is ended with another change without tgss_inactividad or tgss_ctp_huelga. What TGSS clears then is saved as an empty entry dated on the end: the strike row is closed the day before, the strike period is kept in the history and the current value becomes empty.
What to check in your integration: always send tgss_ctp_huelga with inactivity 3, never with 2, and do not use 0/000 for “no CTP” (omit the field). The response of a successful change does not change.