Tenant Policies

Export dynamic policies

Export the organization's policies as JSON: every row the list route returns for the caller, whatever its category, including a row with no category (one written through /api/v1/policies). The same set as /api/v1/policies/export. Before v11.1.0 only rows with a dynamic-* or media-* category were included, and the rest were left out without notice (#4293). This family's import still accepts only dynamic-* and media-* rows and refuses the whole batch at the first other one, so a file that carries other rows is imported through /api/v1/policies/import, which accepts them.

get/api/v1/tenant-policies/export

Request

Headers

X-Tenant-IDstring required
Example:tenant_abc123

Tenant identifier for multi-tenancy isolation. When calling through the Agent (recommended), this header is stamped automatically from the authenticated client — you do not set it yourself. Required only on direct Orchestrator calls (internal deployments).

Response

Exported dynamic policies

exported_atstring date-time
tenant_idstring

Example response

{
  "policies": [
    {
      "id": "pol_abc123def456",
      "name": "Block PII Access",
      "description": "Prevent unauthorized access to personally identifiable information",
      "category": "dynamic-risk",
      "actions": [
        {
          "config": {
            "message": "Request blocked by policy",
            "channel": "security-alerts"
          }
        }
      ]
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.