developers

Official bindings for PHP and .NET, a CLI for automation and AI workflows, and an OpenAPI spec for code generation in any other language. Choose what fits your stack and your release cadence.

Start with the Quickstart

View the OpenAPI spec

PHP SDK

Use the official PHP binding for authentication, document types, webhooks and error handling.

.NET SDK

Use the official .NET binding with the same API coverage as the PHP route.

OpenAPI codegen

Generate a client in Python, Go, Java, TypeScript or Rust from the Swagger spec. Works with openapi-generator, swagger-codegen or similar tooling.

sdks
Official SDKs

Two SDKs with the same coverage as the REST API: authentication, document types, webhooks, validation and error handling. With documentation and examples for a quick start. For any other language, generate a client from the Swagger spec.

Download the OpenAPI spec

cli
CLI for automation and AI agents

The eConnect CLI fits in CI pipelines, scheduled jobs and AI toolchains. Validate documents, send invoices, manage Peppol registrations and retrieve statuses from the command line. Available for Windows, macOS and Linux. AI agents can call it as a tool to autonomously orchestrate e-invoicing processes.

View the CLI documentation

Automation in CI

Call the CLI from your CI environment to make validation checks part of your release flow.

AI agent as tool

Give an AI agent access to the CLI to orchestrate e-invoicing processes: validation, sending and status processing as separate tool calls.

Scheduled jobs

Schedule periodic execution runs or status checks without writing your own integration layer. The CLI handles authentication and retries for you.

PHP or .NET stack

Use the official SDK. This is usually the fastest route to a stable production integration.

Automation or AI

Use the CLI. No integration layer needed, directly executable from pipelines, scripts or AI agent tools.

Other languages

Generate a client from the OpenAPI spec. Works with any modern codegen tool.

choose what fits
Which route fits your team?

Choose based on your development stack and release cadence. For stable integrations with versioned releases, the official SDKs are the safest choice. For automation, scripting and AI applications, the CLI is more accessible. For languages without an official SDK, OpenAPI codegen is the standard route.

View the Quickstart

questions
Frequently asked questions
Where can I find the official SDKs?

The official SDKs can be found via the API documentation at psb.econnect.eu. There you will also find references to examples and implementation details per language.

Which runtime versions are supported?

The current supported runtime versions are listed in the SDK documentation. Always check before planning an upgrade to keep your environment and dependencies aligned.

Can I use the CLI in my existing pipeline?

Yes. The CLI is designed for automation and fits in most CI/CD and scripting environments. Start with a simple validation or sending step and expand from there.

How does an AI agent get access to the CLI?

You give the agent access to a shell or a specific tool wrapper around the CLI. The agent can then call commands for validation, sending or registration checks. Keep acceptance and production credentials strictly separated via environment variables.

Which other languages can I generate from the OpenAPI spec?

Any language supported by openapi-generator or swagger-codegen: Python, Go, Java, TypeScript, Rust, Ruby, Kotlin, Swift and more.

Ask your question

get started
Ready to build?

Start with the Quickstart or request sandbox access directly to experiment with the SDK or CLI.

Start with the Quickstart

Request sandbox access