Skip to main content
Scrive logoeID Hub Documentation

Introduction

Scrive eID Hub is a single API that connects your service to electronic identity providers across Europe. One integration gives you access to 16 eID methods for authentication, identity verification and electronic signing, covering the Nordics, Baltics, Benelux, DACH and the UK.

What eID Hub does​

You call the same REST API regardless of which eID the end user chooses. eID Hub handles the provider-specific protocols, security requirements, QR codes, app switching and error states. Your application creates a transaction, sends the user to authenticate, and reads back the verified result.

Every transaction follows the same lifecycle: new → started → complete or failed. The data you get back depends on the provider, but the integration code stays the same.

Two ways to integrate​

eID Hub Frontend is the recommended path. It's a hosted UI that drives the entire provider flow for you. You redirect the user to a single URL and they come back authenticated. Same code for every provider.

API-only mode is for custom UIs, headless flows or server-driven signing. You control the user experience, but you also own the polling, rendering and provider-specific behaviour.

Both approaches are covered in the Usage section.

What's in these guides​

  • Integration — the transaction lifecycle and common flow shared by all providers.
  • Usage — frontend vs API-only integration, with step-by-step instructions.
  • Authentication — how to authenticate your API requests with bearer tokens.
  • Result handling — how to read transaction results and handle callbacks.
  • Providers — provider-specific details: parameters, data returned, and testing.
  • Multi-Auth Selection (MAS) — let the user pick their eID in a single flow when you support multiple providers.
  • Age Verification & DoB Validation — verify a user's age or date of birth as part of the transaction.

For the full endpoint reference, see the API documentation.