> 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: <https://apidocs.lighter.xyz/docs/get-started>

You can join the Telegram API Channel for updates here: <https://t.me/lighter_api_updates>

### 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 up to 256 API keys.

### Sub-Accounts&#x20;

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.

<br>


---

# 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://docs.lighter.xyz/trading/api.md?ask=<question>&goal=<endgoal>
```

`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.