Skip to main content

When to use this

You already know who the user is and you want the platform to route the request to their wallet for you. The request appears in their wallet, ready to respond.

Endpoint

Request

Request body

Response

201 Created with no body. The request has been queued for delivery.

What happens next

  1. The platform places the request in the user’s wallet. The user does nothing to make this happen.
  2. It appears as pending in their didx:me wallet at $BASE_URL/me-wallet/app, where they review it and share or decline.
  3. You retrieve the result. See Verify presentation, or register a webhook for real-time notifications.
Nothing tells the user the request is waiting. The platform sends no email or push, so they only find it by opening their wallet. Since the request expires 15 minutes after you create it, tell them yourself through a channel they are already watching, or deliver it out of band at the moment they are in front of you.

Troubleshooting

  • 400. The recipient doesn’t match a known user under your organisation for the given identifierType.
Don’t know the user’s identifier, or want them to scan a QR in your UI? Use Deliver out of band instead.