Introduction

Trading clients. Market data. Applications built on Reya.

Build trading clients, market-data tools, dashboards, and automated strategies on Reya's perpetual and spot order book. Connect to the exchange. Stream the market. Make it yours.

This guide covers the order book on Reya mainnet, documenting API 3.6.2. Use devnet1 for integration testing; see Environments. Under Development lists features that are not yet available.

Get started

Quickstart

Read market data, configure an account and signer, submit an order, and track its execution. Start building →

Test on devnet1

Use the same API against devnet1 before going live. Endpoints, chain IDs and contracts for both environments. See environments →

From first request to first order

Start with a public market-data request on mainnet. No account or signer is needed for this step.

Read perpetual market definitions · mainnet

curl --fail --silent --show-error \
  https://api.reya.xyz/v2/perpMarketDefinitions

The response describes the available perpetual markets. Follow the Quickstart to configure an account and signer, submit an order, and track its execution.

Your integration toolkit

REST API

Discover markets, manage orders, and query account data.

WebSocket feeds

Stream order-book updates, order changes, and executions.

Python SDK

Get started with the Python SDK and working examples.

What Reya is

Reya runs a central-limit order book for perpetual futures and spot, matched by an off-chain matching engine (ME) and settled on Reya Network, an Ethereum L2. It is a hybrid system: matching is fast and off-chain, while every resulting trade is independently validated and settled on-chain. The chain is always the ultimate source of truth.

Concretely, as an integrator you:

1. Sign each order as an EIP-712 OrderDetails payload with your trading wallet. (See Signatures & Nonces.)

2. Submit it over REST or the WebSocket Order Entry API — both carry the same payloads and signing rules.

3. The ME matches your order against the book and produces fills.

4. Reya validates each fill for on-chain settlement.

5. Track the settlement outcome and reconcile order state and fills over the WebSocket Info API, and handle the rare trade bust when on-chain settlement rejects a match.

Both perp and spot go through the same path

Perpetual and spot orders share one order-entry surface, one matching engine, and one settlement path. They differ only in the market they target and in a few settlement details. Where the two diverge — for example the marketId namespace (see Market IDs), or the perpExecutions vs spotExecutions channels — the relevant page calls it out explicitly.

How these docs are organised

• Getting Started — quickstart (read market data and submit your first order), the environments and their URLs, the account model, and signer authorization.

• Connectivity — where the ME lives and how to connect, plus heartbeats.

• Authentication — the EIP-712 signing recipe and nonce strategy.

• API Reference — the REST, WebSocket Order Entry, and WebSocket Info references.

• Order Entry — order types & time-in-force, the order lifecycle, and cancel-on-disconnect.

• Executions & Settlement — trade settlement, trade busts, and executions & trade history.

• Pricing & Funding — oracle & index prices, the mark price, and funding.

• Risk — liquidations & ADL and the margin system.

• Reference — market IDs, markets & assets, fees, contract addresses, audits, and the Python SDK 3.6.1.0.

Recommended starting path

If you're integrating for the first time, read in this order:

Quickstart → Environments → Signatures & Nonces → REST API Reference → Trade Settlement → Trade Busts.

The Python SDK 3.6.1.0 is the fastest way to get a correct signature end-to-end.

This guide targets API 3.6.2, preserved in the pinned canonical spec source. The REST and WebSocket spec downloads describe the API currently available at those endpoints, which may differ from this guide; see the Changelog for API changes.

The Python SDK links use release 3.6.1.0, generated from API 3.6.1. See SDK installation and Handling ambiguous outcomes.