AI translation
This page was translated from German with AI. If in doubt, the German original applies.
Developers¶
Technical documentation for connecting your own systems to the ZEDAL platform.
This documentation is aimed at developers integrating a third-party system — ERP, weighbridge software, industry solution, your own business application. It describes interfaces, data formats and call sequences. Guides for working with the ZEDAL apps themselves are in the Manuals.
The fastest way to your first call¶
- Getting started — request access, authentication, first successful call via REST or the .NET SDK.
- Guides — complete processes, step by step:
- Reference — what actually applies when you build the documents.
How this documentation is structured¶
| Section | Answers |
|---|---|
| Getting started | How do I get in? |
| Concepts | How is the platform structured, and what do the terms mean? |
| Guides | How do I complete an entire process? |
| API reference | Which operations exist, and with which signature? |
| Reference | Which values are permitted, and what does this error mean? |
| SDKs | What does the library take off my hands? |
The separation between API reference and Reference is intentional and important: the API reference is generated from the interface definitions and describes signatures — which fields a message has and which type they carry. It says nothing about which values are permitted in business terms and which additional rules the server enforces. That is exactly what the Reference covers.
If you are assembling a DIWASS submission or a consignment note, you need both. The schema alone is not enough to produce a document that is accepted.
Three access paths¶
| Path | When |
|---|---|
| REST / JSON | Any language with an HTTP client. No codegen required, available in production. |
| .NET SDK | C# applications. Encapsulates authentication, token rotation and document handling. |
| gRPC | Type safety through codegen, server streaming, lowest transfer overhead. |
All three lead to the same backend methods and are derived from the same interface definition.
Older documentation¶
The SOAP web service is a legacy interface: it remains supported for existing integrations but is no longer extended. Its documentation is under API reference → SOAP (legacy). New integrations use REST/JSON, gRPC or the .NET SDK.