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

# Send to a path-bound recipient

> Submit a DDN envelope while binding the recipient DID in both the URL and body

This route behaves like `POST /relay`, with one additional safety check: the URL declares the expected recipient. The Relay rejects a message when the path and envelope identify different recipients.

This is helpful when your application routes requests per recipient or wants to detect an accidental body mix-up.

## Request

<ParamField path="recipientDid" type="string" required>
  The URL-encoded recipient DID. It must equal the envelope's `to` or `recipient` field.
</ParamField>

The body is the same encrypted [DDN envelope](/guides/ddn-envelope) accepted by `POST /relay`.

<RequestExample>
  ```bash Request theme={null}
  curl --request POST \
    --url "https://relay.example.com/relay/did%3Atalaria%3A1111111111111111111111" \
    --header "Content-Type: application/json" \
    --data '{
      "message_id": "9f8d6f08-bce5-4df5-b22b-bf8c6bd4e143",
      "to": "did:talaria:1111111111111111111111",
      "timestamp": "2026-07-24T16:30:00Z",
      "payload": {"ciphertext_b64":"<encrypted-message>"},
      "encrypted_header": "<base64-encrypted-header>",
      "header_nonce": "<base64-nonce>",
      "header_key_id": "recipient-key-1",
      "schema_version": "1"
    }'
  ```
</RequestExample>

## Response

The response is the same `DeliveryResult` returned by [Send an encrypted message](/api-reference/relay/send).

## Straight to the point

```http theme={null}
POST /relay/{url-encoded-recipient-did}
```

* Body recipient must equal path recipient
* Success and error schema: `DeliveryResult`
* Use `POST /relay` when path binding provides no benefit