Skip to content
Home / Developer

ZepDesk for developers

Connect your software to ZepDesk. In the Developer Portal you apply to take part, test in your own demo company and submit your app for review. Your app works through the ZepDesk REST API.

STATUSDeveloper Portal open
Sign in to the Developer Portal Apply

For your integration: API documentation

How ZepDesk Developers works

Application

You apply in the Developer Portal with details about your company, your product and the purpose of the connection. Companies whose software complements ZepDesk can take part. We do not accept accounting software.

Developer account and demo company

Once approved, you sign in to the Developer Portal and receive a demo company: your own ZepDesk instance with sample data for developing and testing. If all places are taken, we provide it as soon as one becomes free.

Review and beta

You create your app in the portal and submit it for review. After the first review you can connect it with up to 10 customers whom you invite and we activate. Only apps that process data exclusively in the European Economic Area enter the beta. Your app accesses a customer’s data only after that customer has given consent.

Public under extensions

After a successful beta, at the earliest 30 days after it began, every customer can connect your app. It is then listed under extensions, marked “Developer-App” and labelled “gebaut von” (built by) with your company name.

What we review is described in the manual under Was wir prüfen. How customers connect an app and withdraw access again is described under Developer-Apps verbinden. The terms for ZepDesk Developers apply. These pages are available in German.

The interfaces

REST API with reference

The REST API is versioned. Each company reaches it at its own address in the form https://your-company.zepdesk.de/api/v1/. ZepDesk reads the company from the subdomain, not from the path. You read with GET and write with POST, and every response is JSON with data, meta and errors. ZepDesk generates the API reference from its own routes, as OpenAPI 3.1 in German and English.

Access with API keys

The company’s administrators create keys in ZepDesk on the Interface page, as many as needed, each with its own name and revocable on its own. A key applies only to this company and works with the role chosen when it is created: Accounting, Sales, Tax or Read-only. ZepDesk shows the secret only once. A key cannot reach webhooks, further keys, users or administration settings.

Retries without duplicates

So that a repeated request creates nothing twice, send the X-Idempotency-Key header with a value of its own on every POST. If the same request with the same value arrives again within 24 hours, ZepDesk does not run it again and returns the first response.

Webhooks

A webhook reports events to an https address of your choice, for example to Make, Zapier or your own server. Examples are a paid or overdue invoice, a captured receipt, new bank transactions and an accepted quote. Every message is signed with HMAC-SHA256. The company’s administrators set webhooks up.

MCP for AI programs

With the Model Context Protocol you connect Claude and other MCP-capable programs to your company, at an address of its own in the form https://your-company.zepdesk.de/api/mcp. The program either signs in with your ZepDesk account and then works with your permissions, or it uses an API key with that key’s role. A filing to the tax office stays an open item and goes to ELSTER only after approval in ZepDesk. More under AI assistant and MCP.

Are you planning an app for ZepDesk and have questions? Write to developers@zepdesk.de.