Official PHP and .NET SDKs, OpenAPI codegen for other languages, and the ClientConnector CLI for Windows. There is no cross-platform CLI for every REST call. Choose what fits your stack and your release cadence.
Start with the Quickstart
View the OpenAPI spec
Use the official PHP binding for authentication, document types, webhooks and error handling.
Use the official .NET binding with the same API coverage as the PHP route.
Generate a client in Python, Go, Java, TypeScript or Rust from the Swagger spec. Works with openapi-generator, swagger-codegen or similar tooling.
Two SDKs with the same coverage as the REST API: authentication, document types, webhooks, validation and error handling. Pin NuGet, Composer or generator versions and plan periodic updates. For any other language, generate a client from the Swagger spec.
Download the OpenAPI spec
The ClientConnector is the Windows CLI for folder-based send and receive. It suits legacy on-premise software and automation or AI workflows that do not call the REST API directly. There is no cross-platform CLI for every REST call. For CI validation and sending, use an SDK, a generated client or curl, and start on the acceptance endpoints.
View the ClientConnector docs
Use an SDK, a generated client or curl against the Validate endpoint. The ClientConnector is not a cross-platform CI CLI.
On Windows, an agent can use the ClientConnector for folder-based exchange. For REST calls, use an SDK or a generated client. Keep acceptance and production credentials separate.
The ClientConnector watches local folders on Windows. It does not replace token handling in your own REST client.
Use the official SDK. This is usually the fastest route to a stable production integration.
On Windows, use the ClientConnector for folder exchange. For pipelines and other operating systems, use an SDK, a generated client or curl.
Generate a client from the OpenAPI spec. Works with any modern codegen tool.
Choose based on your development stack and release cadence. For stable integrations, the official SDKs are the safest choice. On Windows, the ClientConnector covers folder-based exchange. For other languages and for CI, use OpenAPI codegen, an SDK or curl.
View the Quickstart
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.
The current supported runtime versions are listed in the SDK documentation. Always check before planning an upgrade to keep your environment and dependencies aligned.
The ClientConnector runs on Windows and exchanges files via local folders. For CI validation or sending on other systems, call the Validate or SalesInvoice endpoints via an SDK, a generated client or curl. Always start on acceptance.
On Windows you can wrap the ClientConnector for folder-based exchange. It does not expose every REST call. For registration checks and other API operations, use an SDK or the OpenAPI spec. Keep acceptance and production credentials separate.
Any language supported by openapi-generator or swagger-codegen: Python, Go, Java, TypeScript, Rust, Ruby, Kotlin, Swift and more.
Ask your question
Start with the Quickstart or request sandbox access to try an SDK or the Windows ClientConnector.
Start with the Quickstart
Request sandbox access