Authentication
The Agent API authenticates with an API key in the X-API-Key header. Operations on a specific organization also require X-Organization-Id.
Headers
| Header | Required | Description |
|---|---|---|
X-API-Key | Yes | Your API key (test or live): app-issued or partner. |
X-Organization-Id | For most operations | UUID of the client organization. Optional for /v1/agent/organizations and company-lookup. |
Key types
| Prefix | Owner | Environment |
|---|---|---|
efk_test_… | Company (app-issued key) | Sandbox: real Peppol TEST network, no credits or billing. |
efk_live_… | Company (app-issued key) | Production: real sending via Peppol. |
efk_pk_test_… | Partner | Sandbox: real Peppol TEST network, no credits or billing. |
efk_pk_live_… | Partner | Production: real sending via Peppol; can manage client organizations. |
Same base URL
https://api.efaktura.sk for both sandbox and production, the environment is determined solely by the key prefix (Stripe model). No separate sandbox domain.Example
curl https://api.efaktura.sk/v1/agent/invoices \
-H "X-API-Key: efk_pk_test_..." \
-H "X-Organization-Id: <org-uuid>"Getting a key
A company with its own system: create both the test and the live key yourself in the app (fa.efaktura.sk → Settings → API keys), active immediately, no approval. A partner: you create sandbox keys yourself in the partner portal, in the API keyssection: they're active immediately. Production (live) partner keys are issued by an administrator after the partner is approved/activated. Not sure which path applies to you? See Access & accounts.
The key is shown only once, at creation, so store it securely. Never embed keys in client-side code or public repositories.