Skip to main content
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

string
required
The URL-encoded recipient DID. It must equal the envelope’s to or recipient field.
The body is the same encrypted DDN envelope accepted by POST /relay.

Response

The response is the same DeliveryResult returned by Send an encrypted message.

Straight to the point

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