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

# Get a recipient delivery policy

> Read the delivery, size, caching, retention, and pricing rules for a recipient DID

A recipient policy tells compatible senders, Relays, and Caches how messages addressed to one DID may be handled. Reading it before sending helps your client choose a valid TTL, keep the message within the size limit, and understand whether Cache fallback is allowed.

## Request

<ParamField path="did" type="string" required>
  The recipient's complete Talaria DID.
</ParamField>

<RequestExample>
  ```bash Request theme={null}
  curl --request GET \
    --url "https://directory.example.com/delivery-policies/recipients/did%3Atalaria%3A1111111111111111111111"
  ```
</RequestExample>

## Response

The response contains the target DID, policy kind, and decoded public policy.

```json 200 Response theme={null}
{
  "did": "did:talaria:1111111111111111111111",
  "scope": "recipient",
  "policy": {
    "effective_ttl": 14400,
    "max_message_bytes": 1048576,
    "cache_eligible": true,
    "replication": 2,
    "encrypted_header_preview_bytes": 256,
    "release_pricing": {
      "base_fee": "100",
      "per_kib_fee": "5"
    },
    "expiration_behavior": "DeleteOnExpiry"
  }
}
```

`effective_ttl` is measured in runtime blocks. Fees are unsigned planck-denominated integer strings.

## Straight to the point

```http theme={null}
GET /delivery-policies/recipients/{did}
```

* Authentication: none
* Body: none
* Success: `200`
* No policy: `404`