> ## 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.

# List actions awaiting endorsement

> Poll this endpoint for status — there is no push notification.

`resourceType` is required: every resource type's ids are bare UUIDs, so `resourceId` on its own
doesn't say which namespace it belongs to. Omit `resourceId` to list every action of that resource
type.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml get /endorsements/actions
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:
  /endorsements/actions:
    get:
      tags:
        - Endorsements
      summary: List actions awaiting endorsement
      description: >-
        Poll this endpoint for status — there is no push notification.


        `resourceType` is required: every resource type's ids are bare UUIDs, so
        `resourceId` on its own

        doesn't say which namespace it belongs to. Omit `resourceId` to list
        every action of that resource

        type.
      operationId: listActions
      parameters:
        - name: resourceType
          in: query
          required: true
          description: >-
            Which namespace to list actions for, and which namespace
            `resourceId` belongs to when supplied.
          schema:
            $ref: '#/components/schemas/ResourceType'
        - name: resourceId
          in: query
          required: false
          description: Filter to actions for this one resource.
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        - name: actionType
          in: query
          required: false
          description: Filter to actions of this action type.
          schema:
            $ref: '#/components/schemas/ActionType'
        - name: status
          in: query
          required: false
          description: Filter to actions in this status.
          schema:
            $ref: '#/components/schemas/ActionStatus'
        - in: query
          description: >-
            When paginating this is used to provide the starting point for the
            page to fetch (retrieved from the previous response body)
          name: after
          schema:
            type: string
            minLength: 1
        - in: query
          name: limit
          schema:
            maximum: 1000
            default: 100
            type: integer
            format: int64
            minimum: 1
          description: Maximum number of results to return per query
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - page
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Action'
                  page:
                    $ref: '#/components/schemas/Page'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          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:
    ResourceType:
      title: Resource Type
      type: string
      enum:
        - ACCOUNT
        - POLICY
        - KEY
        - APPROVAL_GROUP
      description: >-
        Which namespace a resource id belongs to, and which family of action
        types that resource

        participates in:


        * `ACCOUNT` — transaction action types (`WITHDRAWAL`, `DEPOSIT`) and
        trusted-destination
          action types (`TRUSTED_DESTINATION_ADD`, `TRUSTED_DESTINATION_REMOVE`). A trusted destination
          is added to or removed from an account, so such a policy scopes to an account, to any account
          above it, or to the organization — never to an individual destination.
        * `POLICY` — policy-governance action types (`POLICY_CREATE`,
        `POLICY_ARCHIVE`).

        * `KEY` — approval-key-governance action types (`KEY_REGISTER`,
        `KEY_ARCHIVE`).

        * `APPROVAL_GROUP` — approval-group-governance action types
        (`KEY_GROUP_CREATE`,
          `KEY_GROUP_ARCHIVE`).

        For the creation action types (`POLICY_CREATE`, `KEY_REGISTER`,
        `KEY_GROUP_CREATE`) there is no

        resource yet, so a policy's `resourceIds` are the root account ids it
        governs even though its

        `resourceType` names the family being created.
    ActionType:
      title: Action Type
      type: string
      enum:
        - WITHDRAWAL
        - DEPOSIT
        - TRUSTED_DESTINATION_ADD
        - TRUSTED_DESTINATION_REMOVE
        - POLICY_CREATE
        - POLICY_ARCHIVE
        - KEY_REGISTER
        - KEY_ARCHIVE
        - KEY_GROUP_CREATE
        - KEY_GROUP_ARCHIVE
    ActionStatus:
      title: Action Status
      type: string
      enum:
        - PENDING
        - ENDORSED
        - REJECTED
        - EXPIRED
      description: >-
        The action's own lifecycle, distinct from the status of the resource it
        governs. PENDING means it is still collecting endorsements.
    Action:
      title: Action
      type: object
      description: >-
        A change awaiting the endorsements its policy requires. Opened
        automatically by policy evaluation —

        never created directly by a client — and returned as action on the
        response from whichever API the

        change was submitted to.
      properties:
        id:
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        resourceType:
          allOf:
            - $ref: '#/components/schemas/ResourceType'
          description: Which namespace resourceId belongs to.
        resourceId:
          description: >-
            The resource this action governs, in the resourceType namespace. For
            a creation action type —

            POLICY_CREATE, KEY_REGISTER, KEY_GROUP_CREATE — this is the id
            reserved for the resource being

            created: it does not exist yet, but the id is already minted and is
            the one it will carry if the

            action is endorsed. If the action is rejected or expires, that id is
            retired unused.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        subjectId:
          description: >-
            The object this action actually creates or acts on, when that
            differs from resourceId — for

            example a withdrawal, where resourceId names the account whose
            policy governs it. Always

            present: equal to resourceId when the governing and created resource
            are the same thing, as

            for POLICY_CREATE, KEY_REGISTER, and KEY_GROUP_CREATE.


            Equal to resourceId for `TRUSTED_DESTINATION_ADD` and
            `TRUSTED_DESTINATION_REMOVE` as well,

            where it names the account the destination is being added to or
            removed from. The destination

            itself is not identified here: an add is authorized before the
            destination exists, and neither

            action type carries a destination id. So an approver sees which
            account is changing, not which

            destination — if that becomes insufficient, the id has to reach the
            engine on the request

            first.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        actionType:
          allOf:
            - $ref: '#/components/schemas/ActionType'
          description: The action type that triggered this action.
        status:
          $ref: '#/components/schemas/ActionStatus'
        receivedEndorsements:
          type: array
          items:
            $ref: '#/components/schemas/ReceivedEndorsement'
          description: >-
            Every endorsement collected so far — which key, and which group it
            counted toward.
        submittedAt:
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
        expiresAt:
          description: >-
            When this action stops accepting endorsements and becomes EXPIRED.
            Derived from submittedAt plus

            the governing policy's requiredActions.settings.expiresIn, which
            defaults to 14 days when unset.

            Where several policies govern the same change, the shortest of their
            windows is the one applied.
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
    Page:
      title: Page
      description: Pagination info
      type: object
      properties:
        endCursor:
          description: Submit this parameter in the "after" field to fetch the next page.
          type: string
          nullable: true
    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
    ReceivedEndorsement:
      title: Received Endorsement
      type: object
      properties:
        keyId:
          description: The key that endorsed.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        approvalGroupId:
          description: The approval group this endorsement counted toward.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        endorsedAt:
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
  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 action](https://docs.anchorage.com/knowledge-base/api-reference/v4/endorsements/get-an-action.md)
- [Endorse an action](https://docs.anchorage.com/knowledge-base/api-reference/v4/endorsements/endorse-an-action.md)
- [Reject an action](https://docs.anchorage.com/knowledge-base/api-reference/v4/endorsements/reject-an-action.md)
- [Policies and approvals](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-policies.md)
- [Sending assets](https://docs.anchorage.com/knowledge-base/porto/assets/sending-assets.md)
