---
title: "The live tenant policy"
method: GET
path: "/admin/tenant-policies/active"
tags: ["tenant-policies"]
---

# The live tenant policy

`GET /admin/tenant-policies/active`

## Request

- Base URL: `https://api.instruxi.dev/api/v1/enforcer`
- URL: `https://api.instruxi.dev/api/v1/enforcer/admin/tenant-policies/active`
- Auth: API key in header `Authorization`

Returns the tenant's active policy, or null when it has none — which is every tenant until they write one, and so is a 200 with null data rather than a 404.

## Response `200`

OK

- InternalDeliveryHttpHandlerTenantPolicyResponse
  - `data` EnforcerV3InternalDomainTenantpolicyPolicy
    - `accessor_version` integer
    - `activated_at` string
    - `created_at` string
    - `created_by` string
    - `declared_types` string[]: DeclaredTypes are the resource types this policy is authoritative for. Platform types are never here: on those a tenant policy may only DENY, never widen. On a declared type, no policy means no authority.
    - `id` string
    - `retired_at` string
    - `source` string: Source is the Rego verbatim as submitted.
    - `source_sha256` string: SourceSHA256 lets a re-submit of identical text be recognised as a no-op rather than minting a version that changes nothing.
    - `status` string
    - `subject_account_id` string: SubjectAccountID is set when the policy governs one account rather than the tenant. See Subject.
    - `tenant_id` string
    - `validation_error` string
    - `version` integer: Version is monotonic per subject and never reused, because it is what a decision log cites and what an evaluator's cache keys on.
  - `success` boolean
  - `validation` EnforcerV3InternalUsecaseTenantpoliciesResult
    - `declaredTypes` string[]: DeclaredTypes are the resource types the policy is authoritative for, read from its own `declared_types` rule. Platform types are rejected here rather than ignored later: a tenant claiming authority over `account` must be told no, not silently overruled at evaluation.
    - `error` string: Error is why not, phrased for the person who wrote the policy — they cannot see our logs and "compilation failed" tells them nothing.
    - `ok` boolean: OK is whether the policy may be activated.
    - `testsFailed` integer: TestsRun and TestsFailed report the policy's own test_ rules.
    - `testsRun` integer: TestsRun and TestsFailed report the policy's own test_ rules.

## Other responses

- `401`: Unauthorized

---

[API](https://skmtc.dev/instruxi/apis/enforcer-api.md) · [All operations](https://skmtc.dev/instruxi/apis/enforcer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/instruxi/apis/enforcer-api/revisions/fa82bc1becc0?raw)