The demo API
A live insurance API you can call from a browser. Every insurer, vehicle, person and policy in it is invented — it exists to be practised on.
Everything here is synthetic. No real policies, no real people, no real money. Credentials are throwaway and short-lived, and the data you create is deleted when they expire.
Do not enter anything real. Not a real registration number, not a real name, not a password you use anywhere else. There is no reason to, and this is a teaching sandbox rather than a confidential system. What this site does with data.
Get credentials
One request, no sign-up, no email, no terminal. Press the button and you will have a client id and secret you can use immediately.
- Client id
-
- Client secret
-
- Expires
Copy the secret now. It is shown once and is not stored anywhere it can be read back. Losing it costs nothing — press the button again for a fresh pair.
Using these credentials pushes the expiry back, so a session in progress will not be cut off. Leave them unused for a day and they are removed along with any policies you created.
You can still do the whole exercise — the quick-start page documents the credential routes, including the one used in live workshops. Open the demo API quick-start
Then what
Trade the credentials for a bearer token, then create a policy. The quick-start walks through it with copyable commands, and the API's own documentation page runs requests straight from the browser.
- Quick-start — the whole flow, step by step
- API documentation — every endpoint, runnable in place
- cURL cheat sheet — if you prefer a terminal
The one rule worth knowing
A vehicle can hold only one active policy. Insure a vehicle that already has cover and you get a 409 naming a policy you are not allowed to read — try it on ABC-101. That asymmetry is not a bug: a national register tells you a vehicle is insured without telling you whose policy it is. Deciding what an error may reveal is an interface design decision, and it is the one this API exists to make you notice.