Skip to main content
All Zeeg API endpoints require authentication via a Bearer token sent in the Authorization header.

Generating a Token

Create an API token from your Zeeg dashboard: Account Settings > API When creating a token, you select the specific scopes it should have access to. Follow the principle of least privilege — only grant the scopes your integration actually needs.

Making Authenticated Requests

Include your token in the Authorization header of every request. We also recommend setting Accept: application/json.
If the token is missing or invalid, the API returns a 401 Unauthorized response.

Token Scopes

Each token is scoped to specific permissions. The table below lists all available scopes and the endpoints they unlock.
The timetable and booking scopes require a paid Zeeg subscription. If your plan does not include API access to availability slots or programmatic booking, requests using these scopes will be rejected.

Scope Requirements by Endpoint Group

Keep your API tokens secure. Treat them like passwords. Do not commit tokens to version control, expose them in client-side code, or share them in plain text. If a token is compromised, revoke it immediately from the API settings page and generate a new one.
Last modified on April 29, 2026