Policy Application Programming Interface

Use the Policy application programming interface (API) to author and govern policies. Track delivery separately from approval and target protection. Approval establishes a governed revision: the approved version of policy intent. A draft snapshot records saved proposal content, not another approved revision. Compilation produces target output. Publication and target activation happen separately. Begin with authentication and shared contracts.

Choose Your Path

Choose the API reference that matches your task:

• Complete an author-to-reviewer handoff with the worked lifecycle.
• Find an endpoint through the operation directory.
• Correct a failed request with error handling.
• Inspect retained failures through recovery and reconciliation.
• Understand background changes through automatic recompilation.

Operation Families

Choose the reference for the operation you need:

• Catalog, compilation, and preview
• Queries and drafts
• Submission, review, approval, and archive
• History and access
• Product retrieval and compatibility deployment
• Recovery and ownership reconciliation
• Authoring schemas
• Service operations and schema publication

The API base normally uses /pty/policy/v1.0, independently of the application version. Your deployed /swagger page and /doc document expose its schema. Use the endpoint-specific runtime rules here when conditional-header descriptions differ. An entity tag (ETag) is a server-issued resource validator. Draft commands use Draft-ETag. Archive uses the policy ETag. Copy the required token unchanged into If-Match to pin the command to inspected state. Do not substitute the governed policy validator for a current draft token.