Version 1.0 is Live
SAPI-SK

Standardised Access Point Interface

Slovakia | OpenPeppol Community Initiative

Interface Specification for Access Point Providers & Software Applications

OpenAPI 3.0 Specification
SAPI Endpoints
Complete Swagger/OpenAPI documentation for the Standardised Access Point Interface layer

Authentication

  • POST/auth/token
  • POST/auth/renew
  • POST/auth/revoke
  • GET/auth/token/status

Send Document

  • POST/document/send

Receive Document

  • GET/document/receive
  • GET/document/receive/{documentId}
  • POST/document/receive/{documentId}/acknowledge
The Challenge

Market Fragmentation

The Peppol ecosystem lacks a standardised interface between Access Points and software clients

Software Vendors
ERP, accounting & business software

Every AP/SP has proprietary APIs, forcing vendors to:

  • xImplement multiple different integrations
  • xMaintain separate authentication flows
  • xBear increased development costs
AP/SP Providers
Peppol Access Point operators

Market fragmentation creates operational challenges:

  • xComplex partner onboarding processes
  • xInconsistent security implementations
  • xHigher support burden from custom work

Who Benefits from SAPI?

A standardised interface creates value for the entire Peppol ecosystem

Software Vendors
ERP, accounting & business software

Implement once, connect to any SAPI-compliant Access Point:

  • Single integration pattern for all AP/SPs
  • Reduced development and maintenance costs
  • Faster time-to-market for Peppol connectivity
  • Customer flexibility in choosing providers
Access Point Providers
Peppol certified AP/SP operators

Streamlined ecosystem and reduced operational burden:

  • Standardised client onboarding process
  • Consistent security model across all clients
  • Reduced custom integration support
  • Broader software ecosystem compatibility

Brand Assets (WIP)

Display your SAPI-SK compatibility with these official badges

SAPI-SKREADY

Ready Badge

For compliant software

SAPI-SKCERTIFIEDPARTNER

Partner Badge

For AP providers

SAPI-SKinside

Inside Badge

For marketing

SAPI-SK

Standard Logo

For general use

These brand assets will be available for download once the specification reaches stable status.

Important: SAPI is an Interface Specification

SAPI defines interface behaviour and expectations - it is not a central platform, runtime, or hub.

Decentralised Implementation

Each AP/SP remains fully responsible for their own implementation, operation, security, and compliance.

Technical vs Legal Separation

API authentication is separate from legal authority and mandate. SAPI handles technical access only.

Software-Centric Model

Software clients authenticate once, then specify organization context per API call via headers.