Documentation
Integrate the eFaktúra Agent API: issue and send invoices via Peppol, manage customers and documents directly from your application. Start in the sandbox, then switch to production.
Where do you get an API key?
It depends on who you are. A company with its own system (e-shop, ERP) invoicing for itself: your key is right in the app: fa.efaktura.sk → Settings → API keys, no approval needed. A software vendor or white-label partner integrating for multiple companies: the invite-only partner developer portal. The full guide (incl. SAPI-SK): Access & accounts. The documentation below applies to both paths equally.
Quickstart
1. Create a sandbox (test) key: in the app (efk_test_…) or in the partner portal (efk_pk_test_…). 2. Call the API with the X-API-Key and X-Organization-Id headers. 3. Test sending an invoice via Peppol in the sandbox (a real Peppol TEST network, no credits). 4. Once everything works, request a production key.
Access & accounts
Company vs. partner vs. SAPI-SK: who needs what and where to get it.
Quickstart
End-to-end tutorial with curl: org → enroll → invoice → Peppol → status → webhook.
Authentication
API keys, headers, test vs. production.
API keys and scopes
Scope catalog, the default set, and the most common 403 pitfalls.
Invoices
POST /v1/agent/invoices: payload, VAT rates, Peppol completeness.
Receiving and statuses
Send status, incoming documents, and their relation to webhooks.
Validation
Preflight EN 16931 + Peppol check of the UBL XML before sending.
API reference
Complete OpenAPI reference (Scalar) with a live try-it mode.
Webhooks
Events, signing, verification, and delivery retries.
Error codes
Error shape and a reference of all codes.
Rate limits
Limits, headers, and how to handle 429 correctly.
Production onboarding
Getting a company onto live Peppol: FS webhook → email confirmation (claim).
Going live
Checklist for moving from sandbox to production.
Changelog
Dated log of API and portal changes.