> For the complete documentation index, see [llms.txt](https://docs.storm.tg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storm.tg/for-developers/api.md).

# Storm Trade API

Storm Trade provides an open REST API that allows you to connect to the platform, retrieve market data, manage orders and positions, and interact with user data.

The API documentation is available in Swagger format and is continuously updated as new features and improvements are released.

***

## 📄 API Documentation

The official documentation is available here:

🔗 [Storm Trade API Docs (Swagger)](https://api5.storm.tg/api/api-docs)

Within the interface, you will find:

* 📈 Endpoints for accessing **market information**
* 👤 Managing **user data** and positions
* 🧾 Response structures and request parameters
* 🛠️ The ability to **test requests directly in the interface**

***

## 🛠 Usage Examples

The Swagger interface allows you to:

* ⚡️ Quickly test the API without writing any code
* 📦 Generate ready-to-use CURL requests
* 📚 Explore all API parameters and responses

If you are developing an integration, we also recommend checking out the [Storm Trade SDK](/for-developers/sdk.md), which provides a convenient wrapper around the API.

***

> 🧠 **Tip:** Before using the API, ensure that you are working with the latest version of the endpoint and adhering to the request rate limits.


---

# 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.storm.tg/for-developers/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.