# Endpoints

URL: https://postman.slovakodata.com/developers/en/referencia/
Updated: 2026-09-29

Overview of the SAPI-SK and Enterprise API endpoints, with a link to the interactive documentation.

An overview follows. The full reference — schemas, examples and a *Try it*
button — lives in the interactive documentation.

<div class="cards">
  <a class="card card-link" href="/docs/#sapi">
    <span class="chip">standard</span>
    <h3>SAPI-SK <span class="arrow" aria-hidden="true">→</span></h3>
    <p>Eight endpoints of the standardised interface, interactive.</p>
    <span class="card-meta"><code>/docs/#sapi</code></span>
  </a>

  <a class="card card-link" href="/docs/#enterprise">
    <span class="chip chip-neutral">platform</span>
    <h3>Enterprise API <span class="arrow" aria-hidden="true">→</span></h3>
    <p>Invoices, webhooks, notifications, credit and organisation management.</p>
    <span class="card-meta"><code>/docs/#enterprise</code></span>
  </a>
</div>

**Machine-readable specification.** Generating a client? Download the OpenAPI
document directly: [SAPI-SK](/openapi/sapi.json), [Enterprise API](/openapi/enterprise.json),
or [both at once](/openapi.json). The `servers` field is filled in from the
environment you download it from, so a generated client points where it
should.

### SAPI-SK <span class="chip">standard</span>

| Method | Endpoint | Description |
|---|---|---|
| <span class="method m-post">POST</span> | `/sapi/auth/token` | Issues an access token |
| <span class="method m-post">POST</span> | `/sapi/auth/renew` | Renews a token with the `refresh_token` |
| <span class="method m-post">POST</span> | `/sapi/auth/revoke` | Revokes a token |
| <span class="method m-get">GET</span> | `/sapi/auth/token/status` | Reports validity and whether a refresh is due |
| <span class="method m-post">POST</span> | `/sapi/document/send` | Sends a document into the Peppol network |
| <span class="method m-get">GET</span> | `/sapi/document/receive` | Lists inbound documents |
| <span class="method m-get">GET</span> | `/sapi/document/receive/{id}` | Returns the inbound document as JSON (XML in the payload) |
| <span class="method m-post">POST</span> | `/sapi/document/receive/{id}/acknowledge` | Acknowledges the document |
| <span class="method m-get">GET</span> | `/sapi/health` | Service health without authentication — same body as `/health` (200 / 503) |

### Enterprise API

| Method | Endpoint | Description |
|---|---|---|
| <span class="method m-post">POST</span> | `/api/v1/invoices` | Creates and sends an invoice |
| <span class="method m-get">GET</span> | `/api/v1/invoices` | Lists invoices, cursor-paginated |
| <span class="method m-get">GET</span> | `/api/v1/invoices/{id}` | Invoice detail including status |
| <span class="method m-get">GET</span> | `/api/v1/invoices/{id}/xml` | The original UBL XML |
| <span class="method m-get">GET</span> | `/api/v1/invoices/{id}/pdf` | PDF rendering of the invoice |
| <span class="method m-get">GET</span> | `/api/v1/invoices/search` | Full-text invoice search, cursor-paginated; with `scope=archive` across archived invoices instead of current ones |
| <span class="method m-del">DELETE</span> | `/api/v1/invoices/{id}` | Cancels an invoice while still `PENDING` or `VALIDATING` |
| <span class="method m-post">POST</span> | `/api/v1/documents/validate` | Pre-flight validation of a document — no send, no credit |
| <span class="method m-get">GET</span> | `/api/v1/participants/{peppolId}/reachability` | Reports whether the receiver is in the network and supports the document type |
| <span class="method m-post">POST</span> | `/api/v1/webhooks` | Registers a webhook |
| <span class="method m-post">POST</span> | `/api/v1/webhooks/{id}/test` | Sends a test event |
| <span class="method m-get">GET</span> | `/api/v1/billing/balance` | Credit balance |
| <span class="method m-post">POST</span> | `/api/v1/sapi-clients` | Creates a SAPI client |

`documents/validate` and `participants/{peppolId}/reachability` cover the pre-flight
check: they validate the document and the receiver's reachability, create no invoice and
consume no credit. The response shape, the meaning of `reason` and the limits are covered
in [Pre-flight validation](/developers/en/predbezna-validacia/).