15/09/2026 · Certific@2 as JSON

Certific@2 as JSON: new GET /certifica/detail

15/09/2026

Until now, the only thing you could retrieve from a CERTIFIC@2 already filed was the PDF (GET /certifica). The SEPE does not return the original XML, so anyone who wanted the data had to read it off the document.

New GET /certifica/detail: the same parameters as the duplicate (dni, startDate, ccc) and the whole certificate as JSON, without the PDF: company, representative, worker, suspension cause and dates, month-by-month contribution bases, holidays and totals.

GET /certifica/detail
{
  "success": true,
  "message": "OK",
  "status": 200,
  "data": {
    "enterprise": { "cif": "B99999999", "ccc": "281999699", "name": "NOMBRE EMPRESA" },
    "employee": { "nif": "99999999T", "suspension_cause": "02", "suspension_start_date": "2026-07-31" },
    "contributions": [ { "year": "2026", "month": "07", "days": 30, "base_cc": 2583.32, "base_unemployment": 2583.32 } ],
    "holidays": { "days": 0, "base_cc": 0, "base_unemployment": 0 },
    "totals": { "days": 180, "base_cc": 13499.97, "base_unemployment": 13499.97 }
  }
}

Also:

  • GET /certifica (duplicate) adds data.detail with that same structure. file is unchanged.
  • GET /certifica/data is renamed GET /certifica/list, which is what it does. The old name keeps working as an alias, with no removal date for now; the MCP tool sepe_certifica_data likewise stays as an alias of sepe_certifica_list.

Dates as YYYY-MM-DD and amounts as numbers, unlike certificates[], which keeps the SEPE screen format (dd/mm/yyyy).