FIE as JSON: repeated columns no longer lost
03/10/2026
The TGSS FIE report repeats some headers in different sections. With format=json each header was a key, so repeated ones overwrote each other and only the last survived: 85 of the 88 columns came back.
From today the first occurrence keeps its name and the following ones carry their report section code in brackets. Keys still come from the TGSS file itself: if it adds a column or a section, it shows up on its own.
| Key | Section | Before |
|---|---|---|
Entidad Responsable | DIT (Temporary Disability) | Held the DOP section value |
Entidad Responsable (DIP) | DIP (Permanent Disability) | Missing |
Entidad Responsable (DOP) | DOP (Other Benefits) | Came as Entidad Responsable |
Fecha Baja IT | DIT (Temporary Disability) | Held the DIP section value |
Fecha Baja IT (DIP) | DIP (Permanent Disability) | Came as Fecha Baja IT |
The excel format does not change.
What to check in your integration: if you read Entidad Responsable or Fecha Baja IT from the JSON, you used to get the other-benefits or permanent-disability value. It is now the temporary-disability one; for the others, use the keys with (DOP) or (DIP).
FIE by Autorizado RED from MCP
The tgss_excel_fie MCP tool only accepted the company search (regimen + ccc required). It now accepts the same parameters as the endpoint: opcionesBusqueda (0 company, 1 self-employed with naf, 2 Autorizado RED, dates only) and format (excel or json). With opcionesBusqueda: 2 you get the FIE of every company of the certificate's autorizado.
TGSS rejects ranges of 29 days or more with "El rango de búsqueda no puede ser superior a 30 días". So the endpoint maximum drops from 30 to 28 days between startDate and endDate: a longer range returns 422 before calling TGSS, with the same limit over API and MCP.