# Two integration paths

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

Choose based on whether portability or capability matters more to you.

### SAPI-SK v1.0 — standard

The nationally standardised interface. The same code works with any Slovak
provider implementing SAPI-SK. No vendor lock-in.

- OAuth 2.0, request body is a JSON envelope (payload = UBL XML)
- Idempotency required on every send
- 8 endpoints, 19 error codes

### Enterprise API — platform

Our extended interface. Everything SAPI does, plus what the standard
leaves out — events, PDF rendering, credit, archive search.

- Webhooks signed with HMAC-SHA256
- four event types, e-mail and webhook
- PDF rendering and full-text archive search

| Capability | SAPI-SK | Enterprise API |
|---|---|---|
| Portable to another provider | yes | no |
| Request body | JSON envelope (payload = UBL XML) | JSON |
| Authentication | OAuth 2.0 (Bearer) | API key (`X-Api-Key`) |
| Send and receive invoices | yes | yes |
| Event webhooks | no | yes |
| PDF rendering | no | yes |
| Rate limit ([per plan](/developers/en/limity/)) | 10–100 / s per client | 20–200 / s per organisation |

**They combine.** A common setup sends invoices over SAPI-SK — keeping it
portable — while registering webhooks through the Enterprise API, so it
never has to poll for status.