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 user receives a notification and 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 user is notified (typically by email).
  2. Opening the notification routes the request into their wallet.
  3. The user reviews and shares (or declines) the requested credentials.
  4. You retrieve the result. See Verify presentation, or register a webhook for real-time notifications.

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.