Get a recipient delivery policy - Talaria Developer Documentation

curl --request GET \
  --url "https://directory.example.com/delivery-policies/recipients/did%3Atalaria%3A1111111111111111111111"

curl --request GET \
  --url "https://directory.example.com/delivery-policies/recipients/did%3Atalaria%3A1111111111111111111111"

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

string

required

The recipient’s complete Talaria DID.

curl --request GET \
  --url "https://directory.example.com/delivery-policies/recipients/did%3Atalaria%3A1111111111111111111111"

Response

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

200 Response

{
  "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

GET /delivery-policies/recipients/{did}

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

Update the root public key Set recipient delivery policy

⌘I

​Request

​Response

​Straight to the point

Request

Response

Straight to the point