Overview

The Admin API is a read-only, server-to-server JSON API for integration partners (analytics, reporting, channel tools) that need a feed of an organization's bookings and revenue.

It is distinct from the Storefront API (/api/v0/...), which powers customer-facing booking widgets and is scoped to a single location. The Admin API is scoped to the whole organization and is keyed, not location-nested.

Key properties

• Base URL: https://api.servos.dk/admin/v0 (dedicated api subdomain; not org-subdomained)
• Organization-scoped: the organization is derived entirely from the API key. You never pass an organization or location id, and a key can only ever read its own organization's data.
• Read-only: every endpoint is a GET.
• Permissioned: a key reads only the resources it was granted, one permission per resource. See Authentication → Permissions.
• Pseudonymous by default: customers are exposed by a stable, pseudonymous id. Names, emails, phone numbers, and addresses are returned only to a key granted customer_data:read. See Conventions → Customer privacy.

Quick start

1. An organization admin creates a secret key under Settings → API keys, grants it the permissions your integration needs, and shares it with you securely.
2. Authenticate every request with Authorization: Bearer YOUR_API_KEY. The key is scoped to one organization; all data hangs off it.
3. Page through GET /admin/v0/orders for bookings and revenue, or query bookings / stays / tickets directly by visit date.

GET /admin/v0/orders
Authorization: Bearer YOUR_API_KEY

Two views of the same data

• Orders are the transaction/revenue view — one order groups the things bought together, with money.
• Bookings / Stays / Tickets are the booking/visit view — query them directly by visit date (e.g. "sessions next week", "arrivals tomorrow"), each linking back to its order_id and a pseudonymous customer_id.

Use whichever fits; the events feed ties changes across both together.

Guides