Built to be wired in, not bolted on
One REST surface, typed SDKs and a sandbox that behaves like production. Most teams reach a green production call inside a week.
- 01
API overview
A single versioned REST endpoint returns structured JSON with the evidence attached to every field. Requests are idempotent, responses are paginated, and errors are typed so your client can distinguish a transport failure from a decoding failure from a genuine no-match.
- Versioned and backwards compatible
- Idempotent requests
- Typed error envelope
- 02
Integration options
Query synchronously when a user is waiting, submit batch jobs when they are not, and subscribe to webhooks when you want to be told rather than to ask. All three read the same graph and return the same shapes.
- Real-time lookup
- Batch submission with job polling
- Webhook subscriptions
- 03
Authentication and security
Scoped API keys, mutual TLS on request, IP allowlisting and short-lived tokens for browser-side use. Keys are rotatable without downtime and every call is written to an immutable audit record tied to the key that made it.
- Scoped, rotatable keys
- TLS 1.2 minimum, mTLS available
- Per-call audit records
- 04
Developer support
Typed SDKs, an OpenAPI schema you can generate your own client from, and a shared channel with the engineers who maintain the endpoints you are calling. Not a ticket queue.
- OpenAPI schema
- Typed SDKs
- Direct channel to the integration team
- 05
Getting access
Sandbox keys are issued the same day. Production access follows once we have agreed scope, lawful basis and thresholds together - usually within the first week.