> For the complete documentation index, see [llms.txt](https://help.enterprise.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.enterprise.ledger.com/api-documentation-v2/introduction/readme.md). # Getting Started Welcome to the API documentation for Ledger Enterprise Revault. This comprehensive guide will provide you with all the information you need to effectively integrate and use our powerful digital asset custody and trading platform. In this documentation, you will find detailed explanations of our new Revault API endpoints, parameters, and responses. The `revault-api` component is a new iteration of our API that positions Ledger Enterprise for the future, specifically looking to improve: * Read Performance * Up to date data * Future scalability and reliability We have organized the documentation into logical sections to make it easy for you to navigate and find the information you need. Whether you are a developer looking to integrate Ledger Enterprise into your application or a business user seeking to understand the capabilities of our API, this documentation will serve as your comprehensive resource. We have included code examples in multiple programming languages to assist you in making API requests and handling responses. We are committed to providing you with the most up-to-date information, so please check back regularly for any updates or additions to the documentation. We also encourage you to provide feedback, as your input is invaluable in helping us improve and enhance our API documentation. Thank you for choosing Ledger Enterprise. We are excited to have you on board and look forward to helping you unlock the full potential of our crypto custody and trading platform. Let's get started! --- # 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, and the optional `goal` query parameter: ``` GET https://help.enterprise.ledger.com/api-documentation-v2/introduction/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.