Skip to Content
Changelog14/09/2026 · TA duplicate movement

The TA duplicate now says which movement it belongs to

14/09/2026

GET /duplicate-ta returned the TA PDF and, in data.data, every movement for the requested NAF, without saying which one the PDF came from. For a worker with several registrations, whoever received the document could not tell which date it belonged to.

The response now carries data.movement: the specific movement the document was taken from, with its date, its documentoTA and the rest of the screen’s columns.

Respuesta
{ "success": true, "message": "OK", "data": { "data": [ /* todos los movimientos del NAF */ ], "employee": { "name": "...", "doc": "043468731L", "nss": "081524252915" }, "movement": { "indice": 1, "documentoTA": "ALTA (SIT.ACTUAL)", "date": "2023-01-01", "st": "01" }, "file": { "contentType": "application/pdf", "name": "document.pdf", "content": "base64" } } }

It is a new field: data, employee and file are unchanged.

Check movement.date against the date you asked for before treating a movement as filed: the TGSS searches by NAF, so it can return the TA of another registration of the same worker.

Last updated on