How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ledger 4337 API

The 4337 API from Ledger — 5 operation(s) for 4337.

Ledger 4337 API is one of 42 APIs that Ledger publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include 4337. 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 7 operations across 5 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 5.33.1.

Requests are made against the base URL https://api.vault.ledger.com.

7 operations 5 paths 10 schemas 5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.33.1
Base URL
https://api.vault.ledger.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Ledger 4337 API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as sessionid (cookieAuth). An API key is passed in the header as Authorization (tokenAuth).

  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 5 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

4337 7
GET
/tx-service/eth/api/v1/safe-operations/{safe_operation_hash}/
Returns a SafeOperation given its Safe operation hash
safe_operations_retrieve 1 param → 200
GET
/tx-service/eth/api/v1/safe-operations/{safe_operation_hash}/confirmations/
Get the list of confirmations for a multisig transaction
safe_operations_confirmations_list 3 params → 200400
POST
/tx-service/eth/api/v1/safe-operations/{safe_operation_hash}/confirmations/
Add a confirmation for a transaction. More than one signature can be used. This endpoint does not support the use of delegates to make a transaction trusted.
safe_operations_confirmations_create 1 param body → 201400422
GET
/tx-service/eth/api/v1/safes/{address}/safe-operations/
Returns the list of SafeOperations for a given Safe account
safes_safe_operations_list 24 params → 200
POST
/tx-service/eth/api/v1/safes/{address}/safe-operations/
Adds a new SafeOperation for a given Safe account
safes_safe_operations_create 1 param body → 201
GET
/tx-service/eth/api/v1/safes/{address}/user-operations/
Returns the list of UserOperations for a given Safe account
safes_user_operations_list 4 params → 200
GET
/tx-service/eth/api/v1/user-operations/{user_operation_hash}/
Returns a UserOperation given its user operation hash
user_operations_retrieve 1 param → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are UserOperationWithSafeOperationResponse (16 properties), UserOperationResponse (15 properties), SafeOperation (14 properties), SafeOperationWithUserOperationResponse (9 properties). Each schema is shown below with its type and property counts.

SafeOperation
object
Mixin class to validate SafeOperation signatures. getowners can be overridden to define the valid owners to sign
14 properties 14 required
UserOperationResponse
object
15 properties 15 required
UserOperationWithSafeOperationResponse
object
16 properties 16 required
SafeOperationWithUserOperationResponse
object
9 properties 9 required
PaginatedUserOperationWithSafeOperationResponseList
object
4 properties 2 required
PaginatedSafeOperationConfirmationResponseList
object
4 properties 2 required
SafeOperationConfirmationResponse
object
5 properties 5 required
SafeOperationResponse
object
8 properties 8 required
SafeOperationConfirmation
object
Validate new confirmations for an existing SafeOperation
1 property 1 required
PaginatedSafeOperationWithUserOperationResponseList
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ledger-4337-api-openapi.yml Raw ↑

Other APIs Ledger publishes across the network.

Ledger Wallet API
Ledger Device Management Kit
Ledger Accounts API
Ledger Authentication API
Ledger Buy Redirect API
Ledger Capabilities API
Ledger Cardano API
Ledger Compliance API
Ledger Crypto Currencies API
Ledger Currencies API
Ledger Delegates API
Ledger Digests API
Where this information came from

This is an independent, third-party profile of Ledger 4337 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.