21/10/2026 · RED System: Calculations query (settlements, calculations and Bulk query)

RED System: Calculations query (settlements, calculations and Bulk query)

21/10/2026

Three new endpoints under /api/v4/seg-social/ for the RED System service "Cotización SLD Remesas > Consulta de cálculos":

  • GET /contribution-calculations: lists the settlements of a contribution account code in a period. MCP tool tgss_list_contribution_calculations. Documentation.
  • GET /contribution-calculations/detail: calculations of a settlement by concept and list of workers; with naf, the worker detail with their tramos. MCP tool tgss_get_contribution_calculations_detail. Documentation.
  • POST /contribution-calculations/siltra: requests the Bulk query of the calculations of all the workers of a settlement; the TGSS delivers it deferred to the SILTRA mailbox. It is a write (409 if communication with the TGSS is disabled). MCP tool tgss_request_contribution_calculations_siltra. Documentation.

detail always returns workers_list_available: for settlements with many workers the TGSS does not give their list, workers is null and warnings says to query each worker with naf (which works in both cases; a naf outside the settlement gives 404). siltra also works for those settlements. ccc is always 11 digits and liquidation_number 17.

Every object in the response carries an extra field, with the TGSS fields that have no translated key (original XML name, unconverted value; {} if none). If the TGSS adds a new field it shows up there with no API change; if it is translated later, it moves to its English key.

liquidation_number is optional in detail and siltra: if omitted, it is looked up with ccc, regimen, start_date, end_date, liquid_type and liquid_origin; a single settlement is used as is, several give a 422 with data.liquidations to choose from (in the bulk query, with nothing sent to the TGSS) and none gives a 404. Get it with GET /contribution-calculations (data.list[].liquidation_number).

Parameters use snake_case (regimen, ccc, start_date, end_date, liquid_type, liquid_origin, liquidation_number, naf, authorized_num, test). This is an additive change: nothing changes for existing integrations.