Integrate the eConnect PSB API step by step: request a sandbox, authenticate, first API call, send an invoice and test webhooks.
This guide takes you from sandbox request to a working end-to-end flow: token, first API call, invoice send and webhooks. Always start in acceptance (accp- endpoints); production credentials are strictly separate. Why the sandbox exists commercially: All-in-one API.
Request OAuth2 credentials (clientId / clientSecret) via the sandbox wizard. After the request, eConnect creates credentials and a test party on the Peppol test network.
clientIdclientSecretDefault flow for server-to-server: Client Credentials.
accp-psb.econnect.eupsb.econnect.euaccp-identity.econnect.euidentity.econnect.euaccp-vpd.econnect.eu/graphql/v1vpd.econnect.eu/graphql/v1@accp.econnect.email@econnect.emailDocuments from a test account stay on the Peppol test network.
POST /connect/token HTTP/1.1
Host: accp-identity.econnect.eu
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials
&client_id=your-client-id
&client_secret=your-client-secret
&scope=ap
Full path: Authentication.
GET /api/v1/me HTTP/1.1
Host: accp-psb.econnect.eu
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...
Explore endpoints in the interactive API Reference.
POST /api/v1/{partyId}/salesInvoice/send
Body = XML document (Content-Type: application/xml). Recommended first test:
queryRecipientParty (Send invoice)X-EConnect-DocumentId with a UUID for idempotencyNote:
EndpointIDin your XML selects the receiver.
InvoiceSent (or InvoiceReceived)See Configure webhooks.