Account

The human-approval policy of one credential

The credential's stored HITL policy (F46-7b) and the EFFECTIVE one — the union of its own and every ancestor's, which is what actually governs it, because a sub-credential can only ever be tightened.

A marked operation does not run: it becomes an approval request a person decides in the clientarea (API Management → Approvals). Read-only like everything about approvals on this surface: the policy is written in the clientarea, or inherited — narrowed — at mint time, never loosened through the API.

get/credentials/{id}/hitl-policy

Request

  • Base URL: https://api.imprezahost.com/v1
  • URL: https://api.imprezahost.com/v1/credentials/{id}/hitl-policy
  • Auth: API key in header X-API-Key and API key in header X-API-Secret

Response

stored_policy and effective_policy (classes, operations, ttl_minutes)

Changes

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