API guide

Build a consent-led verified profile flow.

Request identity, verification and affordability information for a clear purpose. Tenora only releases the agreed result once the person has approved access.

Request API access Download OpenAPI YAML →

Start here

Simple integration, proper controls.

Production API base URL: https://api.tenora.eu/api/v1. Onboarding issues your organisation a client ID, API secret and only the scopes it needs.

Authenticate

Send X-Tenora-Client and your API secret as a Bearer token. Keep credentials server-side.

Request consent

Create a purpose-led request. Tenora notifies the person and records the approved scope and expiry.

Use the result

Read the safe report once approved. Subscribe to signed webhooks for progress and outcome changes.

Useful endpoints

The routes most teams need first.

GET/checks — available checks and markets

POST/verifications — create a verification

GET/verifications/{verificationId} — progress or outcome

POST/data-access-requests — ask for permissioned report access

GET/data-access-requests/{requestId}/report — approved report

GET / POST/webhooks — signed event delivery

curl https://api.tenora.eu/api/v1/checks \
  -H "X-Tenora-Client: your_client_id" \
  -H "Authorization: Bearer your_api_secret"

Privacy is the product feature.

Reports never expose raw bank transactions, balances or source documents. If an organisation needs access again, the person remains part of the decision.

Back to API access