Introduction
The Ambula API is a REST API over HTTPS for your company’s data in Ambula: conversations (gesprekken), rides (ritten), assignments (opdrachten), contacts, runaways (weglopers) and payments. Use it to keep a BI copy in sync, to plan rides from your own intake form, or to connect a partner’s dispatch tool.
Requests and responses use JSON (application/json). Errors use application/problem+json. All data is scoped to the company that owns the API key.
Environments
Section titled “Environments”| Environment | Base URL | Key prefix |
|---|---|---|
| Production | https://api.ambula.nl/v1 |
amb_live_ |
| Sandbox | https://api.dev.ambula.nl/v1 |
amb_test_ |
A key only works in its own environment. The sandbox runs against a demo company with generated data, and can be ahead of production between releases.
Versioning
Section titled “Versioning”The major version is part of the path. Changes within v1 are additive: new endpoints, new optional parameters and new response fields, so your client must ignore fields it doesn’t know. Breaking changes ship as v2. A deprecated operation returns Deprecation and Sunset headers at least six months before it’s removed.
Your first request
Section titled “Your first request”Create a key in Instellingen → Koppelingen, then list your planned rides:
curl "https://api.ambula.nl/v1/rides?status=planned&limit=1" \ -H "Authorization: Bearer amb_live_<key>"Next, read how authentication works, then the conventions every endpoint follows. The API isn’t public yet: status and availability says what’s coming when.