Skip to main content
didx:me exposes three REST APIs. They share one access token, but each has its own base URL and OpenAPI spec. Every endpoint page below documents its request and response schemas in full.

Consumer Onboarding

Onboard users into your authenticated tenant and look them up by username or external identifier.

Credentials

Issue and revoke credentials, manage templates and presets, and configure endpoints, trusted entities, and certificates.

Presentations

Request presentations and read the proofs holders share back, with reusable templates and presets.

Wallet

Holder-side integration: tenants, wallet credentials, presentations, and organisation flows.

​
Base URLs

All three APIs share one host, and that host differs per environment. Examples throughout these docs write it as $BASE_URL. Substitute the host we gave you when we provisioned your tenant.
Credential offers and presentation requests come back pointing at a different host, the wallet’s invitation entry point, for example creds-app.test.didxtech.com. The API returns that URI and you pass it along unchanged; never construct it, and don’t assume it shares a host with the API.

​
Before you start

Authentication

Every request needs a Bearer access token. Here’s how to get one.
If you’re new to didx:me, the Quickstart issues your first credential in 10 minutes.