ePostman docs
Console

Two integration paths

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

1 min read
  • #sapi-sk
  • #enterprise api
  • #integration
  • #webhooks
  • #portability

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
CapabilitySAPI-SKEnterprise API
Portable to another provideryesno
Request bodyJSON envelope (payload = UBL XML)JSON
AuthenticationOAuth 2.0 (Bearer)API key (X-Api-Key)
Send and receive invoicesyesyes
Event webhooksnoyes
PDF renderingnoyes
Rate limit (per plan)10–100 / s per client20–200 / s per organisation