Developers
Build on the same API the platform runs on
There is no second-class integration surface. The web application talks to the same versioned REST API you are given a key for, which means an endpoint that is good enough for us is what you get too.
Versioned REST
Every endpoint is versioned from the first release. A version stays where it is — new behaviour arrives as a new version rather than as a change under your feet.
Signed requests
Requests are authenticated with a signature computed from your key and the request itself, so a captured request cannot be replayed as-is. Keys are never sent as a bearer secret in the clear.
Scoped keys
A key is issued against your tenant and scoped to the modules your subscription entitles it to. It cannot reach data outside the tenant that issued it.
Live reference docs
The API reference is generated from the running service, not maintained by hand — so what the documentation says and what the endpoint does are the same thing.
Conventions
Boring on purpose
An API you integrate against once and then stop thinking about is worth more than a clever one. These are the rules we hold ourselves to.
Predictable shapes
Successful responses share one envelope. Every list endpoint is paginated — nothing returns an unbounded collection.
Errors you can act on
Failures come back in a standard problem format with a machine-readable type, a human-readable detail and a trace identifier you can quote to support.
Correct status codes
A validation failure is a validation failure, not a 200 with an error inside it and not a 500. You can branch on the status.
Stable identifiers
Resources are addressed by opaque identifiers. Internal structure is never exposed in a URL, so nothing in your integration breaks when ours changes.
Getting a key
Self-service, inside your own tenant
Nobody has to email us to get started, and nobody outside your company can issue a key against your data.
- 1
Sign in to the portal
API access is managed from inside your own tenant by an administrator. There is no separate developer account to create.
- 2
Issue a key
Create a key, see its scope, and revoke it the moment it is no longer needed. Keys are listed with when they were last used.
- 3
Read the live reference
Browse the endpoints your subscription entitles you to, with request and response schemas taken straight from the running service.
- 4
Build
Put your own booking front end, back office or reporting on top — the same API the platform’s own interface is built on.
The full API reference lives inside the product, because what it documents depends on what your subscription includes. Sign in to read it, or talk to us first.
Want to see the API before you commit?
We will walk you through the endpoints that matter for what you are building and tell you honestly whether the platform fits it.