A Request represents the intent of creating or changing an object in the system.For example, when you create a transaction, a *Create transaction* request is created.You can observe all the changes in the system via `GET /requests`.Every request has a `target_type` and `target_id` that you can use to fetchthe object targeted by this request.For example, you can list all requests waiting for approval:```GET /requests?status=PENDING_APPROVAL{ "edges": [ { "cursor": 0, "node": { "created_by": 5, "created_on": "2020-09-25T13:52:38.377654+00:00", "expires_at": "2020-10-02T13:52:38.377605+00:00", "id": 20, "status": "PENDING_APPROVAL", "target_id": 13, "target_type": "USER", "type": "REVOKE_USER" } }, { "cursor": 1, "node": { "created_by": 11, "created_on": "2020-09-25T13:52:53.421567+00:00", "expires_at": "2020-10-02T13:52:53.421502+00:00", "id": 21, "status": "PENDING_APPROVAL", "target_id": 3681, "target_type": "TRANSACTION", "type": "CREATE_TRANSACTION" } } ], "page_info": { "count": 2, "has_next_page": false }}```Here we have 2 requests waiting for approval. You can have more info onthose 2 objects via```GET /users/13GET /transactions/3681```
Ledger Requests API is one of 42 APIs that Ledger publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Requests. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, authentication docs, and rate-limit docs.
This API exposes
8 operations
across 7 paths,
and defines 76 schemas.
It is described by OpenAPI 3.2.0, at version 1.35.0.
Requests are made against the base URL https://api.vault.ledger.com.
8 operations7 paths76 schemas5 GET3 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.2.0
API Version
1.35.0
Base URL
https://api.vault.ledger.com
Authentication
API Key, API Key, API Key
Resource Areas
1
Authentication & Security 3
Ledger Requests API declares
3 security schemes
for authenticating requests.
An API key is passed in the header as X-Ledger-API-User (Ledger_API_User).
An API key is passed in the header as X-Ledger-API-Key (Ledger_API_Key).
An API key is passed in the header as X-Ledger-Store-Auth-Token (Ledger_Store_Auth_Token).
By default, every request must be authenticated.
Ledger_API_User — (required) Username of a registered API User
Ledger_API_Key — If you've set up your API Key when initializing your LAM, you'll need to include it as a header along with the api user header. For more details, [see step 5 o…
Ledger_Store_Auth_Token — If you've set up HashiCorp Vault as an authentication service, you'll need to pass the X-Ledger-Store-Auth-Token header along with the API user header. For mor…
Paths & Operations 8
Across 7 paths, the API surfaces 8 operations — 5 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Requests 8
A Request represents the intent of creating or changing an object in the system. For example, when you create a transaction, a Create transaction request is created. You can obser…
GET
/requests
Search Request
15 params→ 200400
POST
/requests
Create Request
body→ 200400
GET
/requests/{request_id}
Get request by id
1 param→ 200404
POST
/requests/{request_id}/approve
Approve Request
1 parambody→ 200404
GET
/requests/{request_id}/challenge
Get request challenge
1 param→ 200404
GET
/requests/{request_id}/challenge/reject
Get request challenge
1 param→ 200404
GET
/requests/{request_id}/governance-status
Get request's governance progress status
1 param→ 200404
POST
/requests/{request_id}/reject
Reject Request
1 parambody→ 200404
Schemas 76
The contract defines 76 schemas that model the data the API accepts and returns. The most detailed are RequestWithChallenge (10 properties), VaultRequest (9 properties), Request (9 properties), VaultTargetRequest (9 properties). Each schema is shown below with its type and property counts.
SolanaCreateAssociatedTokenAccountTransactionData
object
4 properties3 required
EthereumFeesStrategy
object
2 properties2 required
RequestSearchResult
object
2 properties2 required
PledgeIncrementRequestDataDetails
object
2 properties2 required
ForcedUnpledgeRequestData
object
2 properties2 required
BitcoinSendTransactionData
object
5 properties5 required
CardanoSendTransactionData
object
5 properties5 required
ForcedUnpledgeDetails
object
3 properties3 required
VaultGovernanceStep
object
5 properties4 required
APIRequestChallenge
object
2 properties2 required
PolkadotSendTransactionCreationData
object
3 properties3 required
RippleSendTransactionData
object
6 properties5 required
TezosSendTransactionCreationData
object
4 properties4 required
BitcoinSendTransactionCreationData
object
4 properties4 required
TronSendTransactionCreationData
object
4 properties4 required
EthereumFeesStrategyData
object
2 properties2 required
PolkadotUnbondStakingTransactionData
object
3 properties3 required
CardanoSendTransactionCreationData
object
4 properties4 required
StellarMemoText1
object
1 property1 required
SolanaSendTransactionCreationData
object
3 properties3 required
BitcoinFeesStrategy
object
2 properties2 required
PolkadotBondExtraStakingTransactionData
object
3 properties3 required
APISearchPageInfo
object
2 properties2 required
RequestWithChallenge
object
10 properties7 required
EthereumSCITransactionData
object
7 properties5 required
MessageSigningRequestData
object
3 properties2 required
PolkadotWithdrawTransactionCreationData
object
3 properties3 required
SolanaSendSplTokenTransactionData
object
6 properties5 required
PolkadotWithdrawStakingTransactionData
object
2 properties2 required
TronSendTransactionData
object
5 properties5 required
TezosSendTransactionData
object
5 properties5 required
StellarSendTransactionData
object
6 properties5 required
PolkadotRebondStakingTransactionData
object
3 properties3 required
VaultRequestGovernance
object
3 properties3 required
_RequestApprovePayload
object
1 property1 required
RippleSendTransactionCreationData
object
4 properties4 required
StellarMemoReturn1
object
1 property1 required
GenericFeesStrategyData
object
1 property1 required
StellarSendTransactionCreationData
object
4 properties4 required
TransactionCreationRequestDataV2
object
3 properties2 required
PolkadotChillTransactionCreationData
object
3 properties3 required
StellarMemoId1
object
1 property1 required
PolkadotUnbondTransactionCreationData
object
3 properties3 required
PolkadotSetPayeeTransactionCreationData
object
3 properties3 required
TransactionOrMessageNote
object
2 properties2 required
PolkadotChillStakingTransactionData
object
2 properties2 required
SolanaSendTransactionData
object
5 properties4 required
SCIData
object
3 properties
PolkadotRebondTransactionCreationData
object
3 properties3 required
VaultUserRef
object
1 property
VaultRequest
object
9 properties7 required
MessageData
object
3 properties2 required
SolanaCreateAssociatedTokenAccountCreationData
object
3 properties3 required
EthereumSCDTransactionData
object
5 properties4 required
PolkadotBondExtraTransactionCreationData
object
3 properties3 required
EthereumExecuteContractTransactionCreationData
object
4 properties4 required
EthereumSendTransactionCreationData
object
4 properties4 required
PolkadotSendTransactionData
object
4 properties4 required
_APISearchRequestResults
object
2 properties2 required
Request
object
9 properties7 required
VaultLiteModel
object
1 property1 required
GenericFeesStrategy
object
2 properties2 required
EthereumDeployContractTransactionCreationData
object
4 properties4 required
StellarMemoHash1
object
1 property1 required
BitcoinFeesStrategyData
object
1 property1 required
Error
object
3 properties3 required
SolanaSendSplTokenTransactionCreationData
object
3 properties3 required
ForcedUnpledgeRequestDataDetails
object
2 properties2 required
IncrementDetails
object
5 properties4 required
PolkadotSetPayeeStakingTransactionData
object
3 properties3 required
VaultCollectedApproval
object
3 properties3 required
PledgeIncrementRequestData
object
2 properties2 required
MessageSigningData
object
3 properties3 required
VaultTargetRequest
object
9 properties8 required
EthereumEIP1559FeesStrategyData
object
2 properties2 required
EthereumSendTransactionData
object
6 properties5 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Ledger Requests API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.