API & Integration
Your other systems should not need a person in between.
A versioned REST API scoped to your firm by keys you issue yourself, and outbound webhooks signed so the receiving server can prove where they came from.
For firms with an insurer feed, a broker portal, a bodyshop system, or their own reporting warehouse.
Why it exists
Claims operations accumulate systems. A referral feed from a broker, a bodyshop management system, an insurer’s portal, a reporting warehouse somebody built in a spreadsheet years ago. Each one needs data that lives in the claims system, and the usual bridge between them is a person exporting a file.
That works until volume rises or the person is on leave. What is needed is not a bespoke integration for each — it is a documented interface the other side can build against, with credentials you can revoke without asking anybody.
What it does
The API
- Versioned REST
- Claims, clients, vehicles, hire, documents and intake. Versioned, so an improvement on our side does not break your integration on a Tuesday.
- Scoped to your firm
- A key reaches your data and no other firm's. That is enforced by the database, not by the endpoint.
- Notification of loss by API
- A referring system can create a claim directly, and it arrives tagged as having come from an authorised integration rather than from a public form.
Keys you control
- Issued and revoked by you
- From your own admin screen, without raising a ticket with us.
- Permissions per key
- Thirteen scopes, with read and write always separate. There is no wildcard scope and no admin scope, because a key that can do everything is a key nobody can safely issue.
- Rate limited per key
- Not per address — so one noisy integration cannot starve another.
- Expiry and revocation
- A key can be time-limited, and revoking one takes effect immediately.
Webhooks
- Signed
- Every delivery carries a signature over the payload and its timestamp, so your server can prove a message came from us and was not replayed later.
- Retried
- With backoff, so a brief outage on your side does not lose an event.
- Logged
- A delivery log you can read — what was sent, when, what came back. Which is the difference between debugging an integration and guessing at it.
What changes
Referrals arrive without anybody typing them
And carry their provenance, so a reviewer knows which integration created them.
Your reporting reads from the source
Rather than from a file somebody exported last Thursday.
Access is yours to withdraw
A supplier relationship that ends is a key you revoke, not a support request.
What it does not do
The API covers the claim record and its principal workstreams. It is not a complete mirror of the application — administration, configuration and platform operations are deliberately not exposed, because an API that can reconfigure your firm is a much larger thing to secure.
There is no GraphQL endpoint and no streaming interface. If your integration needs something the current surface does not cover, tell us — the version is there so it can grow.
Related
See it against one of your real claims.
Thirty minutes, no slides. Bring a live file and we will run it through the system end to end.