Read signed policy metadata
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/policy-state';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/policy-state \ --header 'Authorization: Bearer <token>'Reports the activation fence and whether a policy governs actions now. An environment that has never activated a policy answers generation 0, reset_generation 0 and active false. reset_generation belongs to the activation, not the environment: an environment reset ends the activation, and active turns false until a policy is activated again. Activate with the generation read here; read the environment’s own reset_generation from listEnvironments.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Optional for reads after sign-in. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Responses
Section titled “Responses”Successful request
object
The activation fence. 0 means no policy has ever been activated in this environment. An activation request sends the generation it read here.
The environment reset generation the current activation was made in, and 0 when there has been none. It is not the environment’s own reset generation, which listEnvironments reports.
Whether policy_id governs actions now: it was activated in the environment’s current reset generation and every version in its chain is still signed and unrevoked. False when no policy has been activated, after a reset until one is activated again, and after a revocation.
Examplegenerated
{ "org_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "environment_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "generation": 1, "policy_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "review_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "reset_generation": 1, "active": true}Account_changed: reload and review with the signed-in account.
default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}