◆ ePošťák API

How do you want to connect your ERP?

A few simple ways to connect an application or ERP to the Peppol network. Choose what your software can produce.

What can your software produce?

Your choice: Connector

Connector accepts business JSON and manages the standard ERP workflow through delivery, receiving, and business responses.

Why Connector

  • The recommended path for new ERP business JSON
  • customerRef without X-Firm-Id and ordinary recipient IDs
  • Managed send, stage, receiving, status, and business responses
  • SAPI and Enterprise API are full options, no migration needed

Who can pay: The interface does not decide who pays; the type of cooperation in the next step does: the company itself (even when a technical partner connects it), or an integrator for all its companies.

Connector · business JSONillustrative
POST /api/v1/connector/documents
Idempotency-Key: invoice-2026-0042

{
  "customerRef": "erp-vzor",
  "externalId": "invoice-2026-0042",
  "delivery": "send",
  "type": "invoice",
  "number": "2026-0042",
  "issueDate": "2026-07-15",
  "dueDate": "2026-07-29",
  "currency": "EUR",
  "buyerReference": "ODD-IT",
  "recipient": { "country": "SK", "taxId": "2120123456" },
  "lines": [{
    "description": "Mesačná licencia",
    "quantity": 1,
    "unit": "C62",
    "unitPrice": 100,
    "vatRate": 23,
    "taxTreatment": "standard"
  }]
}

Connector is free to try in a sandbox with two test companies.

Who are you connecting and who pays?

Who pays for the API
Your company — by usage

The owner or an admin orders the API in Settings → Connection to an accounting program and creates a key right away. Do you supply software to several companies and each one pastes its own key? You do not need to apply.

Your decision

Connector · I am connecting my own company

Who pays: Your company — by usage.

  1. Order the API in Settings and create an sk_live_* key.
  2. Connect your ERP using the Connector documentation.
  3. Pay only for sent and received documents.
Open API settings
REST API free for testing

Three interfaces. One price.

The sandbox is free. In production you pay only for sent and received documents — no monthly fee and no setup fee.

Full API pricing
BandSendReceive
Band 01
1 – 1 000 docs/mo.
Send0.10 €
Receive0.08 €
Band 02
1 001 – 2 000 docs/mo.
Send0.08 €
Receive0.07 €
Band 03
2 001 – 5 000 docs/mo.
Send0.06 €
Receive0.06 €
Band 04
5 001 – 20 000 docs/mo.
Send0.05 €
Receive0.05 €
Band 05
20 001+ docs/mo.
Send0.04 €
Receive0.04 €

Enterprise add-on — AMQPS/RabbitMQ, Kafka or Edge Connector. An optional Enterprise API extension for AMQPS queues in RabbitMQ, Kafka topics, or a hybrid or on-premise Edge Connector. Implementation, operations, and licence are priced individually based on scope.

How to start

From sandbox request to production

First test the integration safely on the Peppol test network. The agreement and billing come afterwards.

  1. Request a sandbox

    Fill in a short request at dev.epostak.sk/en.

  2. Get free sandbox access

    You receive the account and two test companies by email within minutes. We set up your own company with its real tax ID within 4 hours on a business day; until then, test with the public demo accounts from the documentation. The sandbox is separate from production and creates no commitment.

  3. Test the full flow and choose an API

    Verify sending, receiving and statuses on the Peppol test network. Choose Connector, SAPI, or Enterprise API.

  4. Request production access

    Choose whether the integrator or the individual companies pay. We review the request, agreement and permissions.

Digital mailbox API and e-invoice API in one integration

A digital mailbox API lets an ERP send, receive, and track e-invoices over the Peppol network. An e-invoice API serves the same practical goal: it connects accounting or invoicing software to a certified delivery service without manually re-entering document data.

A simple rule: If your system produces ready UBL 2.1, choose SAPI. If it hands over invoice data as JSON without UBL, choose Connector. Choose Enterprise API when you need to control individual technical steps and webhooks.

◆ Practical questions

What integrators ask most often

Can an ERP automate invitation creation and track its status?

Yes. Enterprise Core API lets an ERP create an invitation for a specific company and track its status using existing partner access. The SAPI standard remains unchanged. An authorized company representative must explicitly accept. Accepted consent does not yet confirm activation and billing are complete. Store the one-time link securely; do not retry invitation creation blindly after an uncertain response. The API documentation provides the workflow and examples under Client onboarding — ERP automation.

Which integration interface should I choose?

Connector is the recommended managed route when an ERP submits business JSON. Choose SAPI if you already create ready-made UBL 2.1 and need the portable Slovak Financial Administration standard. Enterprise API is for integrations that need step-level control, webhooks, preflight, bulk operations, or multi-company management.

What is the difference between Connector, SAPI, and Enterprise API?

Connector turns business JSON into a standard document and manages the usual send, stage, inbox, status, and business-response flow. SAPI transports ready-made UBL 2.1 in its standard envelope and does not create an invoice from business JSON. Enterprise API exposes advanced steps, events, batch operations, multi-company permissions, and document export to accounting programs directly to the integrator.

How do I get sandbox access?

Fill in the short request at dev.epostak.sk/en; access with test companies arrives by email within minutes. Your own company or web inboxes are ready within 4 hours on a business day; until then you can test with the public demo accounts from the documentation. The sandbox is free and does not start a production commitment. Production is activated separately after the go-live review, signature of the selected partner-mode agreement, and Kaja Solutions' countersignature.

Which formats can I send through the API?

Connector accepts business JSON, SAPI transports ready-made UBL 2.1, and Enterprise API accepts structured JSON or ready-made UBL XML depending on the operation. A PDF alone is not an e-invoice; Enterprise tools may use it as an extraction source, but the resulting structured document must still be reviewed and validated.

Does the API cover sending, receiving, and delivery status?

Yes. Connector and Enterprise API cover sending, inbox, events, and document status; SAPI provides its standard sending and receiving operations. Request acceptance or validation is not yet proof of delivery. The integration should follow the subsequent transport status or event.

What happens if the recipient is not on Peppol or does not support the document?

Recipient capability checks and preflight report whether delivery is possible and distinguish a missing Peppol ID, unsupported document type, or temporary lookup failure. If the recipient does not support the required document, ePošťák does not present it as delivered.

Can one integration manage multiple companies?

Yes. A technical partner and a managed integrator each have one key of their own that serves, through SAPI, Enterprise API and Connector, every company that granted them access. With a technical partner each company pays for the API itself; a managed integrator pays for all companies on one invoice. Access always applies only to the specific company and the scope it approved, and the company can revoke it at any time. The partner never receives the company's own key.

Who orders and pays for the API service?

There are three options. A direct company orders the API itself in Settings → API, pays for it and gets its own key (sk_live_*). With a technical partner, each company still pays for itself under the price list, but its software vendor connects it: the vendor signs the no-fee Technical Partnership Agreement and uses one key of its own (sk_int_*) for every company that granted it consent. With a managed integrator, the software vendor pays for all its companies on one invoice. The sandbox is free; production use has been billed since June 1, 2026 under the price list and actual document volume.

I run an ERP for several companies and each company will pay for itself. Should I become a technical partner, or should each company create its own API key?

The price for the company is the same either way (volume-based price list), and as a technical partner you pay nothing. The difference is who does which step. In both cases each company first selects ePošťák as its digital postman on the Financial Administration portal and activates its inbox. Without technical partnership, the company then signs in, accepts the order in Settings → API, generates a key and hands it to you; you manage a separate key per company and depend on the company to rotate or revoke it. As a technical partner you have one key of your own and get test companies in the sandbox. You send the company a connection link, created in the Partner Dashboard or directly from your ERP through the API. The company approves it in one step, which also orders the API for it; it never creates or sends a key. The Partner Dashboard shows every connected company and its connection status, and the company can revoke consent at any time. We recommend technical partnership when you run the ERP centrally and connect several companies. If the ERP is installed separately at each company and you have no central service of your own that the installations talk through, technical partnership usually does not help: each installation should hold that company's own key, because the partner key works for all your companies and should stay under your control only.

Does the ePošťák API support invoice attachments?

Yes. Enterprise API supports up to 20 attachments, 10 MB per file, and 15 MB in total after decoding. An attachment such as a PDF or delivery note supplements the structured invoice but does not replace the UBL document.

Which programming languages have SDKs?

SDKs are available for TypeScript/JavaScript, Python, PHP, C#/.NET, Java, and Ruby. The TypeScript package is published as @epostak/sdk; for the other languages, verify the current version and endpoint coverage in the SDK repository before deployment.

Start with a sandbox request

Fill in a short request at dev.epostak.sk/en and the account with two test companies arrives by email within minutes. We set up your own company with its real tax ID within 4 hours on a business day; until then, test with the public demo accounts from the documentation. The test environment is free and has nothing to do with live invoices.

Who signs and who pays depends on the type of cooperation, not on the interface or data format. A direct company orders the API itself and uses its own key. With a technical partner, the software vendor signs the no-fee Technical Partnership Agreement and each company orders and pays for the API itself by confirming the partner's link. A managed integrator signs the Integrator Agreement and pays for all its companies. White Label (a service under your own brand) is ordered as part of the managed integrator application.