Skip to main content
For current integrations, use GET /policies/v4/application/{applicationId}. URL-encode the Application identifier. This returns the signed document record and finalized block context, with application_id, control_did, and application_revision for the active Application.
Replace the Directory origin and example-app with your registered Application. Read policy_document.document_hex as exact bytes and validate its hash, format, and version before interpreting it. A raw readable record is not execution authorization. A document with unsupported bytes may include validation_error; services must reject it for execution. A cleared record returns cleared: true and suppresses frozen policies for the same scope. A missing document record returns 404 policy_document_not_found; compatible readers can then consider frozen legacy generations. Confirm the Application’s current control DID and status through the Application record.

Legacy compatibility

GET /applications/{applicationId}/policy is a frozen typed-policy reader. When any document record exists for the Application, including a cleared record, it returns 409 policy_document_reader_required. It must not be used to decide that no current policy exists or to resurrect an older rule.

Application boundaries

An Application policy runs event-driven actions independently of recipient routing. It cannot change recipient routes or Cache retention. Send targets must be the control DID or an explicitly linked DID. HTTPS Calls require a bound, active DNSSEC Persona domain owned by the control DID and a permitted destination under that domain. Services recheck current authority before execution. The application receiver defines the meaning of commands such as sendPush; OpenPayload does not send platform push notifications itself. See shared policies and control actions for signed receiver checks and retry semantics.

Straight to the point

  1. Read GET /policies/v4/application/{applicationId}.
  2. Preserve the exact bytes, hash, revision, and finalized context.
  3. Check format, current ownership, and action authority before execution.
  4. Manage publications through the policy document routes.