Request information

Request content

Retrieve content from a specific request by querying the GET request by Id endpoint:

curl --request GET \
  --url https://api.vault.ledger.com/requests/{{request_id}} \
  --header 'authorization: Bearer {{access_token}}' \
  --header 'content-type: application/json' \
  --header 'x-ledger-workspace: minivault'

{
  "created_by": 24,
  "created_on": "2024-01-24T08:07:08.007892+00:00",
  "expires_at": "2024-01-31T08:07:08.007837+00:00",
  "id": 29,
  "status": "PENDING_APPROVAL",
  "target_id": 305,
  "target_type": "TRANSACTION",
  "type": "CREATE_TRANSACTION"
}

Target ID

The attribute target_id of a request in our example of type CREATE_TRANSACTION provides the id of the transaction.

You can search for requests by type, such as CREATE_TRANSACTION, or by status, like PENDING_APPROVAL, to obtain a list of requests awaiting operator approval.

Bash

curl --location 'https://blue-badger-433.minivault.ledger-sbx.com/api-gateway/requests?status=PENDING_APPROVAL&type=CREATE_TRANSACTION' \
--header 'X-Ledger-Workspace: minivault' \
--header 'authorization: Bearer {{access_token}}'

JSON

See who already approved a request

To get the number of request approvers, call the following endpoint:

Bash

curl --request GET \
  --url https://api.vault.ledger.com/requests/{{request_id}}/governance-status \
  --header 'authorization: Bearer {{access_token}}' \
  --header 'content-type: application/json' \
  --header 'x-ledger-workspace: minivault'

JSON

In the JSON data, request ID 62 is completely approved ("is_complete": true). It includes one approval from an operator whose identity is anonymized from my view. The approvers array shows that there were 4 potential approvers for this request, all members of group 11. With a "quorum": 1 and "step_index": 0, we understand that only one approval was needed from all group members for submission.