Quickstart: connect your first integration

This walks through the shortest path from a new account to a working integration.

1. Create an account and an API key

Sign up for an eIDAS Pro account, then generate a merchant API key from your dashboard. Every authenticated request to the verification API sends this key as the x-merchant-api-key header — see API keys for how keys are scoped, rotated, and revoked.

2. Check which verification methods are live for your deployment

Availability depends on deployment stage: a fresh deployment may have no verification method configured yet, and which methods it does have depends on which broker credentials are set up for it. GET /api/config is unauthenticated and is the authoritative, live source of truth — treat it as the first call you make, not an afterthought:

curl https://api.eidas-pro.com/api/config

Read the supportedMethods field in the response. An empty array means no method is configured for this deployment yet; an entry such as "idin" means that method is ready to accept requests. Don't assume any particular method — including iDIN — is enabled without checking this first, and re-check it if a request later fails with a method-related error.

3. Choose one of the three integrations

Pick whichever matches your storefront:

• WooCommerce — a WordPress plugin.
• Shopify — a Shopify app.
• JavaScript widget — drop-in script for any other stack.

Each integration wraps the same verification API, so you only need to follow one of these three guides to get a working checkout gate.

4. Start a verification session

If you want to see the API respond before wiring up an integration, start a session directly. The request body's required field is verificationType, one of age, country, or both (see what eIDAS Pro does for which of these the currently implemented path actually serves):

curl -X POST https://api.eidas-pro.com/api/verification/init \
  -H "x-merchant-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "verificationType": "age"
  }'

method (one of eudi, idin, itsme) is optional and lets you target a specific verification method explicitly instead of taking the deployment's default; only request a method that supportedMethods from step 2 actually lists. A successful call returns a session ID and an authorization URL for the customer to complete the check.

If something is wrong with the request — an invalid key, a malformed body, or a method that isn't configured for this deployment — the API responds with a consistent error envelope instead of a bare HTTP status:

{
  "error": {
    "message": "A human-readable description of what went wrong",
    "code": "SOME_STABLE_ERROR_CODE",
    "statusCode": 400
  }
}

Branch your integration's error handling on code, not on message — message is for humans and can be reworded, code is the stable token. If you hit an error you don't recognize, check troubleshooting before opening a support ticket.

5. Confirm the result

Poll or listen for the result of the session you created:

curl https://api.eidas-pro.com/api/verification/{sessionId}/result \
  -H "x-merchant-api-key: YOUR_API_KEY"

The result is deliberately narrow: a session status plus two booleans, verified and thresholdMet. It never includes a country code, a date of birth, a name, or any other personal attribute — merchants only ever get a pass/fail signal, by design. That's a complete round trip — from here, wire the same calls into whichever integration you chose in step 3.