> ## 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 credential offer to a known user by email, username, or external identifier.

## When to use this

You already know who the user is. They have an account in your organisation, and you want the platform to deliver the offer to their wallet for you. No QR codes, no copy-paste.

The user receives a notification (typically email) and the credential arrives in their wallet.

## Endpoint

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

## Request

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

### Request body

| Field             | Type   | Description                                                                                                                             |
| ----------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| `credentialOffer` | string | The `offerUri` returned by [Issue a credential](/products/didx-me/guides/issuers/issue-credential). 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 offer has been queued for delivery.

## What happens next

1. The user is notified (typically by email).
2. Opening the notification routes the offer into their wallet.
3. The credential appears as **pending** in the wallet, ready for accept/reject.

## Troubleshooting

* `400`. The `recipient` doesn't match a known user under your organisation for the given `identifierType`.
* `403`. Your organisation isn't authorised to issue this credential to this user.
* Credential never arrives. Verify that `credentialOffer` is the plain `offerUri` and not the QR variant.

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