Developer documentation

One platform for all your digital ID needs

The fast track for organisations to achieve authentication in all channels. Access multiple identity services with a single integration.

Contact Scrive sales for API credentials, then test against our testbed environment before going live.

How it works

Every identification or signing session follows the same pattern, whichever provider you use.

01
Create a transaction
Start an authentication or signing session via the API with your chosen provider and parameters. Receive a generated URL in return.
02
Direct the user
Redirect the end user to the generated URL. They complete their identification or signing with their chosen eID provider.
03
Receive the result
The user is forwarded back to your redirect URL after authenticating. Poll the transaction or use webhooks to get the verified result.

Start here if this is your first eID Hub integration.

What you need in place before you start, and the first calls to make once you have it.

A working integration you can run against the testbed with your test credentials.

The reference material behind an eID Hub integration.

The concepts and flows behind an integration, explained in longer form.

Every endpoint, parameter and response, generated from the OpenAPI spec.

Integrate through OIDC instead of the REST API, using your existing client library.

One integration, every provider below. Each page covers behaviour, test data and what the provider returns.

Keep track of API changes, and get help when something does not add up.

How API versions are released, and what to expect when one changes.

Support articles for eID Hub, and how to reach Scrive when you need a person.