Skip to Content
Changelog03/11/2026 · SEPE extensions: discontinuidad is no longer mandatory in the API

SEPE extensions: discontinuidad is no longer mandatory in the API

03/11/2026

Affects POST /api/v4/sepe/prorroga (Extension) and its MCP tool. Corrects what was stated on 20/10/2026.

  • No more own 422 without discontinuidad. Previously, if the SEPE form had the field and you did not send it, the API responded 422 without reaching SEPE. The extension is now sent stating there was no discontinuity.
  • The field depends on the contract, not on a date gap. SEPE shows it for certain contracts even when the extension starts the following day; in that case, without discontinuity, the communication goes ahead normally.
  • N is valid again and is equivalent to not sending the field.
  • If there is a date gap, SEPE requires S and, if it does not receive it, rejects the communication with “Debe indicar el campo discontinuidad”. That rejection is returned like any other SEPE rejection.

What to check in your integration: nothing if you already omitted the field when there was no inactivity. Send S only if there was inactivity that justifies the discontinuity; if SEPE responds “Debe indicar el campo discontinuidad” and there was none, correct the dates so the extension starts the day after the end of the contract or of the last extension.

Last updated on