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

# Developer overview

The Developer section is for teams **integrating with Exliquid**, not for developing the Exliquid chain implementation.

Typical integrations include:

* trading terminals;
* market-making and execution bots;
* portfolio and account tools;
* analytics and monitoring applications;
* automated test and research clients.

## Integration surfaces

Exliquid exposes three primary client surfaces:

### SDKs

Maintained TypeScript and Python SDKs help construct signed actions, call REST endpoints and consume WebSocket data.

See [SDKs](/docs/developers/sdk.md).

### REST API

The `/api/v1` contract provides network, market, account, transaction, liquidation, authorization and testnet-faucet operations.

See [REST API](/docs/developers/rest-api.md).

### WebSocket

The `/ws/v1` contract provides low-latency market and authenticated account streams with snapshot/delta/resume semantics.

See [WebSocket](/docs/developers/websocket.md).

## Recommended integration flow

1. Read [Networks and versions](/docs/reference/networks-and-versions.md).
2. Use a supported SDK or implement the published API/signing contract.
3. Query market metadata and account state.
4. Obtain the correct nonce for the account/signer/action domain.
5. Build an explicit action.
6. Sign the typed transaction.
7. Submit it with an idempotency key.
8. Retain the transaction ID while confirmation is unknown.
9. Wait for committed confirmation.
10. Reconcile the resulting order, balance or position state.
11. Use WebSocket for low-latency updates and resynchronize on sequence gaps.

## What you do not need to integrate

External applications do not need to understand or depend on:

* validator process topology;
* the internal consensus adapter;
* mempool implementation;
* internal databases or storage layout;
* node recovery algorithms;
* Exliquid source package structure.

If an integration starts depending on one of those details, it is probably depending on the wrong contract.

## Public endpoint policy

A route shape can be documented before a public base URL is opened. The current public base URLs and supported SDK versions are authoritative only when listed in [Networks and versions](/docs/reference/networks-and-versions.md).


---

# 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://exliquid.gitbook.io/docs/developers/overview.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.