Before you start, you need the
clientId and clientSecret DIDx issued for your organisation, and the host for
your environment. Both arrive through partner onboarding. There is
no self-serve signup.client_credentials flow on the Authentication page. Tokens last five minutes. If you take longer, re-run the auth call and re-export.
Issue the credential
1
Onboard yourself as a user
The Consumer Onboarding API provisions users in your tenant. For this quickstart, you’ll provision yourself.Response (201):
emailSent: true means your onboarding link is on its way. tempPassword comes back empty on this pathway. It only carries a value on the older temp-password flow.2
Complete onboarding and sign in
Check the inbox for the address you just onboarded. You’ll have an onboarding email with a single-use, time-boxed link.Follow it to set your own password, verify your email, and configure strong auth. That lands you in the didx:me wallet at
$BASE_URL/me-wallet/app. It runs in any browser, and opening it on your phone is closest to how holders will use it.You’ll see an empty wallet: your name in a welcome banner, with No credentials yet below. Keep this tab open. If you close it, go back to $BASE_URL/me-wallet/app and sign in if it asks you to.3
Create a credential preset
A preset is the published shape of the credential: its format, attributes, and disclosure rules. Publish it once, then issue many credentials against it. The platform manages the underlying template for you.Each attribute takes a JSON key (the field name inside the credential payload) and a few properties: Colours must be 6-digit hex. You can also set
type is the JSON type, name is the display label shown in the wallet, required controls whether issuance demands a value, and alwaysDisclosed controls whether the attribute travels on every presentation or only when a verifier asks for it. An optional description adds wallet-side helper text, which this example omits. See Credentials for the selective-disclosure model behind alwaysDisclosed.The response includes the preset’s id, in the form YOUR_TENANT_ALIAS:demo, and its templateType, which is the credential type URL the platform built from your code. Save both. The id identifies what to issue, and the templateType is what you ask for when you verify.templateName is the preset’s display name. The inner templateAttributes.name defines an attribute called name. They are different scopes and don’t collide in JSON.Optional: style the card
The credential above uses the wallet’s default card styling. To control how it looks, add abranding block next to templateAttributes:backgroundImageUrl. Add it now if you want it, because branding is fixed at creation like everything else on a preset, and adding it later means publishing a new preset under a new code. See Branding for the full set of fields and the rules on background images.4
Create an issuance
An issuance binds a preset to a specific set of values for one credential.Ignore
reference is how you name what to issue: KIND:VALUE, where kind is presetId, templateId, or credentialType. Pass more than one entry in credentials to bundle several credentials into one offer. See Issue a credential for the other reference kinds.The response (201) includes the offerUri:credentialTemplateId for now. The platform manages that template for you. It only matters if you later want to list everything issued from this preset; see Issuance vs credential.The offerUri points at a creds-app.* deep-link host, the wallet’s invitation entry point, which is a different host from $BASE_URL. You pass this URI along unchanged; never construct it yourself.Save the offerUri.5
Push the offer to your wallet
Send the credential offer directly to your wallet. It will appear in the Pending state in your wallet.A
201 Created with { "data": null } confirms that the platform delivered the offer.6
Accept the credential in the wallet
Switch to the wallet tab. Refresh if needed. A Pending Credentials section now shows a card for your DEMO credential.Tap into the card. The detail view shows the claims (Name, Surname) and credential information. Tap Accept.The credential moves from Pending to Recent. You now have a verifiable credential signed by your tenant, held in your wallet.
Verify the credential
You will now play the verifier against the credential you just issued, using the same preset-then-reference pattern as the first half.1
Create a presentation preset
A presentation preset is the published shape of a request: which credential type to ask for, which attributes you want back, and whose signature counts as proof. It mirrors the credential preset you published earlier.Pass the The response includes the preset’s
templateType you saved as type. The two must match exactly, because that is how the wallet works out which credentials could answer the request.id, in the form YOUR_TENANT_ALIAS:demo-request. Save it.This preset names no
trustedIssuers, which means it accepts a DEMO credential from any issuer. That keeps the quickstart short, and the last step shows you what it costs. A real verifier always lists the issuers it accepts. See Trust.2
Create a presentation request
A request turns the preset into one live question for one person.Response (201):Save the
id, which you read the result with, and the authorizationRequestUri, which you deliver.3
Deliver the request to your wallet
Send the request to the same user you onboarded at the start.A
201 Created with { "data": null } confirms that the platform delivered the request. As with the credential offer, delivery is not an answer. The request is now waiting in the wallet for you to respond.4
Share the credential from the wallet
Switch to the wallet tab and refresh. A Pending Credential Presentation Requests section appears. Tap View Requests.The request shows who is asking and which attributes they want. Your DEMO credential is the only one that matches, so the wallet has already selected it for you.Tap Share.
5
Read the verified result
Back in your terminal, read the result as the verifier.
status is verified and isValid is true, so the credential is cryptographically sound and the attributes are the ones you asked for. That is the full round trip.Two details in that response are worth understanding before you build on it.The attributes map carries a status claim you never asked for. That is the revocation pointer the platform checks on your behalf, and it is an object rather than a string. Read the fields you asked for by name instead of looping over everything the map happens to contain.trustSignals is empty. The credential is valid, and you still know nothing about whether its issuer is one you should accept, because your preset named no trusted issuers. Closing that gap is what Trust is for.What next
Once the quickstart works, here are the common next moves:- Trust hardening. Your demo request accepted any issuer, which is why it came back with no trust signal. Name the issuers whose credentials count as proof so that anything else is rejected. See Trust.
- Webhooks. Your application learns about issuance lifecycle events (
offered,completed,failed,expired) without polling. See Webhooks. - The full journeys. The quickstart took one path through each side. For the rest, including QR delivery, see the Issuer journey and the Verifier journey.
- Production readiness. Rotate certificates and set up retry policies on your webhook handler. Talk to DIDx when you’re ready to move beyond your initial environment.

