> ## Documentation Index > Fetch the complete documentation index at: https://docs.parmanasystems.com/llms.txt > Use this file to discover all available pages before exploring further. # List authority grants > Lists every authority grant, active and revoked: which caller may have which capability decided, within which limits, from when until when. ## OpenAPI ````yaml openapi.bundled.yaml GET /authority-grants openapi: 3.1.0 info: title: Parmana API version: 1.0.0 description: > Parmana sits between an AI agent and the systems it acts on. An agent sends a Business Transaction: who authorized it, what action it wants, and the facts that justify it. Parmana evaluates the policy bound to the action, checks any signed human approval the policy requires, releases the action to the connector only if the policy approves, and returns a signed Execution Trust Record anyone can verify. **Authentication.** Send `Authorization: Bearer ` on every request. The only routes that need no key are the probes, the documents and the independent verification routes: `GET /health`, `GET /ready`, `GET /openapi.yaml`, `GET /openapi.json`, `GET /api-manifest.json`, `GET /documentation`, `GET /reference`, `GET /parmana-handbook.pdf`, `GET /handbook/download-leads`, `POST /handbook/download-leads`, `POST /refusal/verify`, `POST /execution-intents/verify`, `POST /audit/verify`, `GET /keys/{keyId}` and `GET /.well-known/jwks.json`. A missing or unknown key returns `401` before anything else runs. The server holds only a hash of each key. See [Authentication](/api-reference/authentication). **Two kinds of key.** An agent or service key may invoke only the capabilities listed on it. A human key (`credentialHolderType: USER`) is required for governance: proposing and approving policies, approvers and external connectors, and repairing Execution Intents. Approving or rejecting a change also needs a step up authorization signed with the checker's own step up key, and the checker must not be the person who proposed it. **Ownership.** Every lookup by `businessTransactionId` is scoped to the key that submitted the transaction. A transaction submitted by another key returns the same `404` as one that does not exist. **Try it live.** The first server below is the public sandbox, `https://parmana-sandbox.vercel.app`: the same code as production with its own database, keys and demo approver, whose one action, `sandbox:receipt`, acts on nothing. Every "Try it" panel calls it with the published demo key prefilled. The demo key may invoke only `sandbox:receipt`, so other capabilities return `403` and governance routes return `403 NON_HUMAN_CALLER_DENIED`. Everything sent to the sandbox is visible to every visitor. See [Playground](/playground). Production needs a key issued by its operator. **Start here:** the [Playground](/playground) (no install), the [Quickstart](/quickstart), then [Integrate Parmana](/agents/integrate) for agents and [Connect any external system](/guides/connect-any-external-system) for your own endpoint. contact: name: Parmana Systems email: founder@parmanasystems.com license: name: Proprietary, source-available for evaluation only, see LICENSE url: https://github.com/pavancharak/parmana/blob/main/LICENSE servers: - url: https://parmana-sandbox.vercel.app description: >- Public sandbox (the docs playground). Same code as production, demo data only, acts on nothing. Demo key prefilled. - url: https://parmana-api-real.vercel.app description: Production. Needs a key issued by the operator. - url: http://localhost:3000 description: Local (packages/api, PORT env var, default 3000) security: - bearerAuth: [] tags: - name: Execution description: >- Executes a Business Transaction through the complete Execution Trust pipeline - name: Transactions description: Business Transaction creation and retrieval - name: Verification description: Deterministic verification of an Execution Trust Record - name: Receipts description: Cryptographically signed Execution Trust Receipts - name: Trust Records description: Execution Trust Record retrieval - name: Replay description: Deterministic replay of a recorded Execution Trust Record - name: Policies description: Policy existence/readability check - name: Policy Governance description: Maker-checker proposal, listing, approval, and rejection of policy changes - name: Approvers description: Maker-checker for the keys trusted to sign approvals, without a deploy - name: External Connectors description: >- Maker-checker for binding a capability to an operator's HTTPS endpoint and its policy, without a deploy (ADR-0013) - name: Business Signal Sources description: >- Maker-checker for the business systems Parmana asks for the facts a policy needs, without a deploy (RFC-0023) - name: Authority Grants description: >- Maker-checker for which agent may have which action decided, within which limits, until when (RFC-0023) - name: Sandbox description: >- Routes that exist only on the public sandbox (ADR-0014), for trying Parmana from a browser - name: Refusal Records description: >- Durable, signed evidence that a policy decision rejected a transaction (RFC-0021) - name: Execution Intents description: >- A signed statement, stored before an action is released, of exactly what is about to be released, plus the operator tools to find and repair a released action that has no signed Trust Record (ADR-0012) - name: Audit description: >- Signed caller-authentication audit events, independently third-party-verifiable - name: System description: Operational endpoints paths: /authority-grants: get: tags: - Authority Grants summary: List authority grants description: > Lists every authority grant, active and revoked: which caller may have which capability decided, within which limits, from when until when. A grant matters only under a policy with `requireAuthorityGrant`. Revoked grants stay listed, so every decision that rested on one can be explained. Needs a human key. See [Grant an agent authority](/guides/grant-an-agent-authority). operationId: listAuthorityGrants responses: '200': description: The grants. content: application/json: schema: $ref: '#/components/schemas/authority-grants-list-response.schema' examples: active: summary: Real captured response value: grants: - grantId: 9f3cf733-a8ed-487c-bb58-a53950388cdf callerId: warehouse-agent capability: erp:release-goods limits: parameters.amount: max: 100000 parameters.currency: oneOf: - INR validFrom: '2026-10-11T03:29:05.247Z' validUntil: '2026-12-30T00:00:00.000Z' status: active grantedAt: '2026-10-11T03:29:05.247Z' withRevoked: summary: >- Real captured response, after a revoke: the grant stays listed value: grants: - grantId: 9f3cf733-a8ed-487c-bb58-a53950388cdf callerId: warehouse-agent capability: erp:release-goods limits: parameters.amount: max: 100000 parameters.currency: oneOf: - INR validFrom: '2026-10-11T03:29:05.247Z' validUntil: '2026-12-30T00:00:00.000Z' status: revoked grantedAt: '2026-10-11T03:29:05.247Z' revokedByChangeId: 77a3b517-4ae0-4c72-8f0c-5aa6ed913df1 revokedAt: '2026-10-11T03:29:05.300Z' '401': $ref: '#/components/responses/Unauthorized' '403': description: '`NON_HUMAN_CALLER_DENIED`: this needs a human key.' content: application/json: schema: $ref: '#/components/schemas/error.schema' examples: service: summary: Real captured response, a service credential value: error: >- This action requires a caller credential provisioned as a verified human (credentialHolderType: USER). code: NON_HUMAN_CALLER_DENIED x-codeSamples: - lang: bash label: cURL source: |- curl https://parmana-api-real.vercel.app/authority-grants \ -H "Authorization: Bearer $PARMANA_API_KEY" - lang: typescript label: TypeScript source: |- import { ParmanaClient } from "@parmana/sdk"; const client = new ParmanaClient({ endpoint: "https://parmana-api-real.vercel.app", apiKey: process.env.PARMANA_API_KEY!, }); for (const grant of await client.authorityGrants()) { console.log(grant.callerId, grant.capability, grant.status, grant.validUntil); } - lang: python label: Python source: |- import os from parmana import ParmanaClient client = ParmanaClient( endpoint="https://parmana-api-real.vercel.app", api_key=os.environ["PARMANA_API_KEY"], ) for grant in client.list_authority_grants(): print(grant.caller_id, grant.capability, grant.status, grant.valid_until) components: schemas: authority-grants-list-response.schema: title: Authority Grants List Response description: 'Response of GET /authority-grants: every grant, active and revoked.' type: object additionalProperties: false required: - grants properties: grants: type: array items: $ref: '#/components/schemas/authority-grant.schema' error.schema: title: Error Response description: >- Shared error envelope produced by packages/api/src/middleware/error-handler.ts and by every route's inline validation checks. error is always a plain human-readable string (never a nested object). code is present only when the failure was a RuntimeError subclass reaching the centralized error handler (VerificationFailedError, ReceiptGenerationError, or an uncategorized RuntimeError); it is absent from every inline route-level check (businessTransactionId format/required checks) and from BusinessTransactionValidationError, PolicyValidationError, SignalValidationError, PolicyNotFoundError, DuplicateBusinessTransactionError, and the generic 500 fallback. POST /policies/validate does NOT use this envelope at all. See its own response schema. For the triggering condition and recommended caller action behind any specific error/code/status combination, see the Error catalog at /api-reference/error-catalog. type: object additionalProperties: false required: - error properties: error: type: string description: Human-readable error message. code: type: string description: >- Stable machine-readable error code. Only present for errors that reach the handler as a RuntimeError. examples: - RUNTIME_ERROR - VERIFICATION_FAILED - RECEIPT_GENERATION_FAILED - POLICY_DENIED - CAPABILITY_NOT_ALLOWED - RATE_LIMITED - AUDIT_UNAVAILABLE - SIGNING_UNAVAILABLE - CONNECTOR_NOT_REGISTERED - EXECUTION_RECORD_INCOMPLETE - EXECUTION_INTENT_UNAVAILABLE - EXECUTION_INTENT_RESULT_NOT_RECORDED - EXECUTION_INTENT_NOT_FOUND - EXECUTION_INTENTS_NOT_ENABLED - EXECUTION_INTENT_NOT_RESOLVABLE - EXECUTION_INTENT_RESOLUTION_INVALID - NON_HUMAN_CALLER_DENIED - EXECUTION_OUTCOME_UNKNOWN - AUTHORIZATION_NO_LONGER_VALID executionStatus: type: string enum: - EXECUTION_UNKNOWN - NOT_EXECUTED description: >- RFC-0023 phase 4. EXECUTION_UNKNOWN with EXECUTION_OUTCOME_UNKNOWN: the action was released and the call failed, so whether it ran is unknown; never reported as failed, and the Execution Intent stays ERRORED until a person resolves it. NOT_EXECUTED with AUTHORIZATION_NO_LONGER_VALID: the release was refused because a business condition or the authority grant it rested on no longer held, and nothing was sent. examples: - error: businessTransactionId must be a valid UUID. - error: >- Business Transaction 'eed2a972-1bf5-4166-8472-761f76fbf1b2' already exists. - error: >- Execution rejected: Vendor payment rejected because the assessed payment risk exceeds the maximum permitted threshold. code: RUNTIME_ERROR authority-grant.schema: title: Authority Grant description: >- Authority granted to one caller for one capability, within limits, until an expiry (RFC-0023 phase 3), made through authority grant changes. A policy with requireAuthorityGrant decides a request only when its authenticated caller holds a grant in force and the request is within its limits. Nothing is deleted: a revoked grant stays listed. type: object additionalProperties: false required: - grantId - callerId - capability - validFrom - validUntil - status - grantedAt properties: grantId: type: string description: The changeId of the approved grant change that created it. callerId: type: string description: The callerId of the API key the grant is for. capability: type: string pattern: ^[a-z][a-z0-9]*(?:[-_][a-z0-9]+)*:[a-z][a-z0-9]*(?:[-_][a-z0-9]+)*$ limits: type: object description: >- Limits on the request, by Intent path: target or parameters.. min and max (inclusive) apply to a number there; oneOf lists the only values allowed there. A request whose value is missing, of another type, or outside a limit is NOT_AUTHORIZED. maxProperties: 32 propertyNames: pattern: ^(?:target|parameters\.[A-Za-z_][A-Za-z0-9_]{0,63})$ additionalProperties: type: object additionalProperties: false minProperties: 1 properties: min: type: number max: type: number oneOf: type: array minItems: 1 maxItems: 64 items: type: - string - number validFrom: type: string format: date-time description: 'From when it holds: the proposal''s validFrom, or the approval time.' validUntil: type: string format: date-time description: >- Until when it holds. After this, requests are refused as AUTHORITY_EXPIRED. status: type: string enum: - active - revoked description: >- At most one active grant per caller and capability. Active says not revoked; check validFrom and validUntil for whether it is in force. grantedAt: type: string format: date-time revokedByChangeId: type: string description: 'revoked only: the approved change that revoked it.' revokedAt: type: string format: date-time description: revoked only. responses: Unauthorized: description: >- The `Authorization` header is missing, is not a bearer key, or names a key the server does not know. Nothing ran. Send a valid key. content: application/json: schema: $ref: '#/components/schemas/error.schema' examples: authRequired: summary: Real captured response, missing or invalid Authorization header value: error: authentication required securitySchemes: bearerAuth: type: http scheme: bearer x-default: 2VfYWCzt_cBAPK-8uufX6ordfY2JuQhFPsohuEumKME description: > Caller API key issued by scripts/generate-api-key.ts. Sent as Authorization: Bearer . Verified against a stored SHA-256 hash in constant time by packages/api/src/auth/StaticKeyAuthenticator.ts. Required on every route not listed as exempt in this document's top-level description. See /api-reference/authentication. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.