> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didx.co.za/llms.txt
> Use this file to discover all available pages before exploring further.

# Deliver via identifier

> Deliver a presentation request to a known user by email, username, or external identifier.

## 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

```
POST https://test.didxtech.com/me-wallet/api/orgs/presentations
```

## Request

```bash theme={null}
curl -X POST "https://test.didxtech.com/me-wallet/api/orgs/presentations" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "presentationRequest": "https://test.didxtech.com/invitation?request_uri=...",
    "recipient": "[email protected]",
    "identifierType": "email"
  }'
```

### Request body

| Field                 | Type   | Description                                                                                                                                                                    |
| --------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `presentationRequest` | string | The `authorizationRequestUri` returned by [Create a presentation request](/products/didx-me/guides/verifiers/create-presentation-request). The plain link, not the QR variant. |
| `recipient`           | string | Identifier value for the user                                                                                                                                                  |
| `identifierType`      | string | One of `email`, `username`, `externalIdentifier`. Defaults to `email`                                                                                                          |

## 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](/products/didx-me/guides/verifiers/verify-presentation), or register a [webhook](/products/didx-me/guides/webhooks) for real-time notifications.

## Troubleshooting

* `400`. The `recipient` doesn't match a known user under your organisation for the given `identifierType`.

<Tip>
  Don't know the user's identifier, or want them to scan a QR in your UI? Use [Deliver out of
  band](/products/didx-me/guides/verifiers/deliver/out-of-band) instead.
</Tip>