> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/trading/api.md). # API You can find the Lighter API Documentation here: You can join the Telegram API Channel for updates here: ### API Keys Each account and sub-account on Lighter may interact with the exchange using Lighter API keys. These API keys are owned by the account and are used to sign requests when interacting with the exchange. Signed requests are verified by the exchange to confirm authorization by the API key holder and the associated account. Each account or sub-account may register API keys at indices 0–254. Indices 0–3 are reserved for Lighter's web and mobile apps, leaving 251 for your own use. ### Sub-Accounts To create a Lighter account, users must have an Ethereum wallet. Using this wallet, users register a main account by signing a message that associates their Ethereum address with Lighter. Assets can then be deposited by sending a transaction from the wallet to Lighter’s smart contracts. In addition to the main account, users may create multiple sub-accounts linked to the same Ethereum wallet. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lighter.xyz/trading/api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.