For Developers (API)

daagwerk provides a full REST API – the same one the web and mobile apps are built on. Ideal for connecting daagwerk to your own tools.

Interactive API reference (Swagger)

The complete, always-current reference with “Try it out”:

→ https://api.daagwerk.de/docs

Every endpoint is documented with a description, parameters, response types and error codes. The OpenAPI specification is available at https://api.daagwerk.de/docs/doc.json.

Base URL & format

https://api.daagwerk.de

All responses are JSON. All endpoints except /auth/* and /health require a valid token. Dates use the format YYYY-MM-DD.

Authentication (JWT)

POST /auth/login
Content-Type: application/json

{ "email": "du@example.com", "password": "•••••••" }

GET /entries?from=2026-01-01&to=2026-01-31
Authorization: Bearer <dein-token>

Typical endpoints

Purpose	Endpoint
Structure	`GET /accounts`, `GET /projects/{id}/jobs`
Time tracking	`POST /timers/start`, `PUT /timers/{id}/stop`, `POST /entries`
Entries	`GET /entries`, `PUT /entries/{id}`
Reporting/Export	`GET /reports`, `GET /export/entries.pdf`, `GET /export/entries.csv`
Purchase orders	`GET /purchase-orders`, `POST /purchase-orders`

Roles & visibility

The API respects the same roles as the app: it only returns sensitive fields (e.g. hourly rates) to managers and above; all data is strictly limited to your own tenant.

Notes

Errors come back as JSON with a descriptive error code.
The API documentation is deliberately in English – the endpoint descriptions are detailed and also suitable for AI / “vibe coding” tools.