Skip to content

Control Plane API

The Control Plane API is the Policy Administration Point (PAP): the system of record for organizations, projects, schemas, policies, entities, tokens, and audit history. Your services call it with an app token to manage schemas, policies, and entities, and to read audit history. People use the Console.

  • Versioned base path: all endpoints live under https://api.zstrike.io/api/v2026-01/.

  • Required headers: every protected request sends Authorization, x-op-id (an ID for the operation) and x-session-id (an ID grouping related operations). A request missing either ID header is rejected with 400.

  • Consistent envelope: successful responses carry the same shape:

    {
    "success": true,
    "code": "S200",
    "description": "…",
    "data": { },
    "timestamp": "…"
    }

Your services and automation authenticate with an app token: Authorization: Bearer <token>, using a token created in the Console.

App tokens are JWTs scoped to your organization or to a single project, with:

  • a fine-grained permission map: for each resource, the allowed verbs:

    Resource Verbs
    policies, entities, tests, test_data read, write, delete
    schema, projects read, write
    audit read
    inline_entities assert (send inline resource entities to the PDP)
  • a mandatory expiry: tokens cannot be minted without one;

  • rotation and revocation: rotating issues a new secret (same scope, permissions, and expiry) and invalidates the old one immediately; revocation takes effect immediately.

Only organization owners and admins can manage tokens, in the Console. The secret is shown exactly once, at creation (and again on rotate). A token’s scope, permissions, and expiry can’t be edited: create a new token and revoke the old one. Destructive operations require the matching permission. For example, a batch request that deletes entities needs the entities: delete grant, not just write.

See App tokens for how to create, rotate, and revoke tokens, and exactly which endpoints each grant unlocks.

App tokens work on the endpoints in the API reference. An organization-scoped token calling a body-based ingest endpoint must name the project as projectId in the request body. A projectId query parameter is rejected with 403.

Area Capabilities
Projects List and create projects, and update their details.
Schemas Read and update the project’s Cedar schema; versioned.
Policies Create, update, delete, list (search, sort, filter, paginate), and version Cedar policies; impact analysis before saving.
Entities Full CRUD on individual entities, search, plus bulk batch and reconcile ingestion.
Sessions List sessions, read their activity, and reset a session.
PDP Attach a project to a shared regional PDP and read the attachment.
Audit Query decision history and aggregate summaries. See Audit.

Everything else is done in the Console: your organization and its members, app tokens, test data and the simulator, AI-assisted policy generation, PDP client token rotation, and trusted identity providers.

The full endpoint list is in the API reference.

Policies are validated, and can be described honestly

Section titled “Policies are validated, and can be described honestly”

Policy and schema writes are validated with Cedar. A write that doesn’t validate is rejected. You can also opt in to description verification by sending verifyDescription: true with a policy create or update. If the description doesn’t match what the policy actually does, the API rejects the write and returns a suggested description. Verification is off by default.

The Control Plane API deliberately makes no runtime authorization decisions for your applications. Decisions belong to the Policy Decision Point, which syncs from the control plane and answers locally. This split is what lets the data plane keep answering even when the control plane is unreachable.