Skip to main content
Get an application policy
The V3 response below is available on the USE2 OpenDispatch Directory with the production spec 123 chain. Read the active application’s policy from finalized chain state. The shared V3 policy map stores one policy per application_id. Its owner is the registered control DID. The Application policy applies independently of the recipient’s DID or Persona policy. Read the application record to confirm its control DID and status. An Application policy supplies third-party metadata and control instructions. It does not route messages or change Cache retention. Register the Application through the Directory, then manage its V3 policy through the policy routes. This endpoint is read-only.

Request

string
required
Lowercase application identifier containing 1 through 64 letters, digits, dots, underscores, or hyphens.

Response

The policy’s rules and payload templates define the control action. Send delivers an encrypted control DDN envelope to its named recipient DID. Call sends a signed HTTPS request to a DID service endpoint on a domain registered to the policy owner. See shared policies and control actions. The application service decides what sendPush means; OpenPayload does not send a push notification itself. policy_ttl_seconds is the maximum time a Cache may reuse this policy lookup. It is separate from message retention. A missing or inactive application policy returns 404.

Straight to the point