> For the complete documentation index, see [llms.txt](https://help.multisig.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.multisig.ledger.com/reference.md).

# Reference

The Ledger Multisig Transaction Service API provides a comprehensive suite of endpoints designed to orchestrate the lifecycle of multi-signature transactions. It serves as the backend infrastructure for tracking Safe accounts, managing pending signatures, and broadcasting fully executed transactions.

This reference documentation details every available endpoint, enabling you to build custom integrations, automate treasury flows, or develop interface extensions on top of the Ledger Multisig ecosystem.

#### Supported Networks & Endpoints

The Ledger Multisig API is deployed across multiple EVM chains. While the endpoint structure remains consistent, you must target the specific `chain_id` or base URL corresponding to your desired network.

Use the selector below to identify the correct Chain ID for your requests:

| Supported Network          | Chain ID  |
| -------------------------- | --------- |
| Ethereum Mainnet           | 1n        |
| Base                       | 8453n     |
| Arbitrum                   | 42161n    |
| Polygon                    | 137n      |
| Optimism                   | 10n       |
| Ethereum Sepolia (testnet) | 11155111n |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.multisig.ledger.com/reference.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.