REST API for individual ZEP integrations

With the ZEP REST API, you connect ZEP to your own systems, tools, and workflows. Read, write, and update projects, times, employees, invoices, and more — programmatically, scalably, and according to modern REST standards.

Access to all central ZEP resources via REST endpoints
Seamless integration into your own products, portals and system landscapes
Full OpenAPI specification and developer documentation available

Über 3.000 Unternehmen vertrauen auf ZEP

Benefits of ZEP REST API

Everything you need for powerful ZEP integration—in a modern API standard.

Extensive resources and endpoints

  • Access to projects, project times, employees, customers, invoices, receipts, absences, and more
  • Read, write and delete operations for all central ZEP objects
  • Endpoints for Master Data, Finances, Personnel Management, and Configuration

Easy start for developers

  • Token-based authentication via bearer token — set up quickly
  • Pagination and query parameter filtering according to REST standards
  • Download the OpenAPI specification for quick integration into existing workflows

Flexible for individual requirements

  • Provide your own products, customer portals or internal tools directly with ZEP data
  • Automate data maintenance, reporting, and system reconciliation
  • Scalable for small teams as well as for complex corporate landscapes
ZEP Logo

ZEP in vollem Funktionsumfang 14 Tage kostenlos testen

Häkchen-Symbol
GDPR-compliant
Häkchen-Symbol
Hosting and development in Germany
Häkchen-Symbol
30 day trial without obligation

How to get started with ZEP REST API

zep-Logo in der Mitte umgeben von Logos der Schnittstellen Partner

Set up REST API and send the first request

To use the REST API, you need the ZEP additional module “ZEP Interfaces”, which you can activate via the self-service tool. After activation, you generate an API token in ZEP and can immediately make initial requests to the API.

The complete developer documentation including all endpoints, authentication details, and the OpenAPI specification can be found in our Developer Hub.

Mehr Infos im Help Center

FAQ

Frequently asked questions and answers about the ZEP REST API.

What use cases is the ZEP REST API suitable for?

The REST API is suitable for companies that want to deeply integrate ZEP into their system landscape — for example through their own evaluation tools, customer portals, automated synchronization with CRM or HR systems, or individual workflows involving project time and billing. Software providers and ZEP partners also use the API to integrate ZEP functionality into their own products.

What is the difference between the ZEP REST API and the ZEP SOAP API?

Both APIs provide programmatic access to ZEP data, but differ in technology and focus of application. The REST API is more modern, lightweight and particularly suitable for new integrations, web applications and individual tools. The SOAP API is based on the established W3C XML standard and is particularly suitable for enterprise and legacy systems that already support SOAP natively.

What data can I read and write using the ZEP REST API?

The ZEP REST API provides access to all central resources: projects, project times, employees, customers, invoices, invoice items, receipts, absences, tickets, offers, departments, locations, activities, price groups and more. Read, write, and delete operations are available for most resources.

Can I retrieve project controlling data automatically via the ZEP REST API?

Yes With the REST API, projects, project times, invoices, invoice items, receipts and employee sales can be programmatically retrieved and transferred to your own controlling or BI systems. This enables automated evaluations and reports without manual data export from ZEP.

How can project time recording be integrated into your own systems via the ZEP REST API?

The ZEP REST API provides dedicated endpoints for reading, creating and changing project times. In this way, recorded working hours can be automatically transferred to external systems or written from third-party systems to ZEP — without manual export. The API follows modern REST standards and is secured by a bearer token.