> For the complete documentation index, see [llms.txt](https://docs.alcor.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alcor.exchange/developers-api/api.md). # API **New API v2 docs can be found here**: [api.alcor.exchange](https://api.alcor.exchange) Alcor Exchange has HTTP and WebSocket api. Alcor Exchange provides an API for the UI view reasons charts/lates deals/orderbook. etc. But as Alcor is DEX any intereation with blockchain, such as new order or order cancel, requires work with blockchain node api directly. Some examples can be found in "None API" page. **HTTP API URL are separated by chains using following structute:** ``` chain_name: Name of chaing api to interact with. 1. wax 2. proton 3. telos 4. eos (default, no need chain_name to specify) .alcor.exchange/api // Example wax.alcor.exchange/api proton.alcor.exchange/api ``` WebSocket endpoint uses the same structure but has /socket.io/ at the end, example: ``` wss://wax.alcor.exchange/socket.io/ ``` --- # 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://docs.alcor.exchange/developers-api/api.md?ask= ``` 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.