Roadmap
Which parts of the API are live today, and which are still planned.
This site started as a target design, written before any of this existed in SUMU_Backend. That's no
longer true: as of staging commit d1f8cb5, most of /v1/api is real, working code — not a spec
waiting to be built.
Live in code today: taxpayer onboarding and Peppol registration, documents/validate, JSON invoice
sending (POST /invoices) including saving as a draft, dry-running a payload or
uploading a spreadsheet of many at once, raw UBL sending (POST /documents),
one unified feed for everything sent or received (List transactions,
Get a transaction), document downloads — the transmitted XML, the Tax Data
Document, and a rendered PDF (Download a document) — webhooks, and
participant lookup all exist and match this reference for the shapes described on each page. Check with
the team on current public staging-host reachability before pointing an external integrator at it.
Bulk upload and transaction ordering aren't on any branch on GitHub yet
Bulk upload and the order filter on
List transactions are documented from real, captured responses off a
running deployment — not invented — but as of this writing neither exists on staging, dev,
e-invo, or main in the SUMU_Backend repository on GitHub. Confirm with the backend team which
branch actually holds this code, and that it's been pushed, before relying on it outside that
deployment.
Still genuinely not built: an access-control model for organisations that want to issue scoped,
restricted credentials rather than one all-access key per organisation — see the callout on
Authentication. And there is no dashboard UI anywhere to create an
organisation or mint its first API key — the backend admin endpoint that does this is real, but nothing
in SUMU_Frontend calls it (also flagged on Authentication). Today,
provisioning an integrator means an engineer calling that admin endpoint directly.