> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get an approval key

> Fetch a single approval key of the caller's organization by id, in any status. A key of another
organization is not found. The caller's key must hold `READ_IAAS_POLICY_ENGINE` or
`MANAGE_IAAS_POLICY_ENGINE`.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml get /approvers/keys/{keyId}
openapi: 3.1.0
info:
  title: Anchorage Digital Account APIs (v4)
  version: 4.0.0-beta
  description: >-
    Reference for the Anchorage Digital v4 API, the surface behind Crypto as a
    Service: account management (accounts and the account tree, beneficiaries,
    freeze/unfreeze/close), balances and transactions, trusted destinations,
    orders and allocations, withdrawals, deposit instructions, deposit
    attributions, the policy engine (policies, approval keys), and supported
    asset types. Approval groups, endorsements, compliance profiles, customers
    (onboarding), fee configuration updates, interest enrollment, funding
    allocations, and destination removal are under construction and return
    mocked data only.


    Status: BETA. The v4 API is available in the sandbox only
    (https://api.anchorage-staging.com/v4) and is not available in production
    yet. The contract may change until general availability. Which endpoints are
    live, in final testing, or under construction:
    https://docs.anchorage.com/platform/developers/caas/caas-overview


    Authentication: every request carries an `Api-Access-Key` header. Every
    POST, PATCH, and DELETE additionally requires an `Idempotency-Key`, and is
    signed with `Api-Signature` (hex-encoded Ed25519 over
    `timestamp_epoch_seconds + uppercase(http_method) + request_path +
    request_body`) plus `Api-Timestamp` (unix epoch seconds).


    Pagination: list endpoints accept `after` (cursor) and `limit` (page size, 1
    to 1000, default 100) and return a `page.endCursor` to continue from. Errors
    use a common envelope with a human-readable `message`; batch endpoints
    return a result per item instead.


    Guides: https://docs.anchorage.com/platform/developers/caas/caas-overview
servers:
  - url: https://api.anchorage-staging.com/v4
security:
  - Api-Access-Key: []
tags:
  - name: Accounts
  - name: Compliance Profiles
  - name: Balances
  - name: Transactions
  - name: Trusted Destinations
  - name: Orders & Allocations
  - name: Withdrawals
  - name: Deposit Instructions
  - name: Deposit Attributions
  - name: Policies
  - name: Approval Groups
  - name: Endorsements
  - name: Customers
  - name: Asset Types
paths:
  /approvers/keys/{keyId}:
    get:
      tags:
        - Approval Groups
      summary: Get an approval key
      description: >-
        Fetch a single approval key of the caller's organization by id, in any
        status. A key of another

        organization is not found. The caller's key must hold
        `READ_IAAS_POLICY_ENGINE` or

        `MANAGE_IAAS_POLICY_ENGINE`.
      operationId: getApprovalKey
      parameters:
        - name: keyId
          in: path
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          required: true
          description: Unique identifier for the approval key
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/KeyResponse'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
components:
  schemas:
    KeyResponse:
      title: Approval Key Response
      type: object
      required:
        - data
      properties:
        data:
          $ref: '#/components/schemas/Key'
    ErrorDetails:
      title: ErrorDetails
      type: object
      properties:
        message:
          description: A human-readable message providing more details about the error.
          example: Missing required field 'amount'.
          type: string
      required:
        - message
    Key:
      title: Approval Key
      type: object
      required:
        - id
        - status
        - organizationId
        - apiKeyId
        - publicKey
        - label
        - createdAt
      properties:
        id:
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        status:
          $ref: '#/components/schemas/KeyStatus'
        organizationId:
          type: string
          pattern: ^[0-9a-f]{64}$
          description: The organization key id the approval key is registered in.
        apiKeyId:
          type: string
          pattern: ^[0-9a-f]{64}$
          description: 'The approver''s API key id: hex-encoded SHA-256 of its access key.'
        publicKey:
          type: string
          pattern: ^[0-9a-f]{64}$
          description: The key's Ed25519 public key, lowercase hex-encoded (32 bytes).
        label:
          type: string
          description: >-
            A name for the key, used only in audit records. It does not identify
            the key holder.
        approvalGroupId:
          pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
          description: >-
            The approval group the key belongs to, fixed at registration. Absent
            on a key registered before approval groups existed.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        createdAt:
          description: >-
            When the key was registered. Lists are ordered newest first on this
            value, then by `id`.
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
        archivedAt:
          description: When the key was archived. Present only when `status` is `ARCHIVED`.
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
    KeyStatus:
      title: Approval Key Status
      type: string
      enum:
        - ACTIVE
        - ARCHIVED
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [Get an approval group](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/get-an-approval-group.md)
- [Policies and approvals](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-policies.md)
- [List approval keys](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/list-approval-keys.md)
- [Archive an approval key](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/archive-an-approval-key.md)
- [Register an approval key](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/register-an-approval-key.md)
