This guide explains how to integrate a market making system with the Ekiden REST and WebSocket APIs. It provides an overview of authentication, market data, order management, private account streams, and operational best practices. Detailed endpoint specifications, request parameters, and response schemas are available in the API Reference.

1. Overview

Ekiden provides REST and WebSocket APIs for low-latency market making and automated trading.

Supported Protocols

REST API (HTTPS)
WebSocket (WSS)

Environments

Environment	REST	WebSocket
Testnet Beta	`https://api.cnt.ekiden.fi/api/v1`	`wss://api.cnt.ekiden.fi/ws/public` `wss://api.cnt.ekiden.fi/ws/private`
Staging	`https://api.canton.ekiden.fi/api/v1`	`wss://api.canton.ekiden.fi/ws/public` `wss://api.canton.ekiden.fi/ws/private`

Public market data is available without authentication. Trading operations and private account streams require authentication.

2. Authentication

Ekiden supports two authentication methods:

JWT Bearer authentication
API Key authentication

Obtain a JWT

POST /api/v1/authorize

Example request:

{
  "public_key": "<Canton Party ID>",
  "signature": "",
  "timestamp_ms": 1731541800000,
  "nonce": "random-unique-string"
}

Successful response:

{
  "token": "<jwt>",
  "user_id": "<user_id>"
}

The returned JWT is used to authenticate private REST requests and private WebSocket connections.

REST Authentication

Authenticated REST requests use the standard Bearer header:

Authorization: Bearer <jwt>

API Key Authentication

REST API Key authentication uses the following headers:

X-API-KEY
X-SIGNATURE
X-TIMESTAMP-MS
X-NONCE

The signature must be an Ed25519 signature of:

EKIDEN_API|{method}|{uri}|{timestamp_ms}|{nonce}

Refer to the Authentication guide for complete details.

3. REST API

REST endpoints are grouped by resource.

Group	Purpose
`/market/*`	Public market data
`/order/*`	Order management
`/execution/*`	Trade execution history
`/position/*`	Positions and leverage
`/account/*`	Account balances
`/user/*`	User resources

Example:

curl \
  -H "Authorization: Bearer <jwt>" \
  "https://api.cnt.ekiden.fi/api/v1/position/list?sub_account_address=<SUB_ACCOUNT_ADDRESS>"

Refer to the API Reference for complete endpoint documentation.

4. WebSocket

Ekiden provides separate public and private WebSocket endpoints.

Endpoint	Authentication
`/ws/public`	Not required
`/ws/private`	JWT or API Key

JWT Authentication

Authenticate immediately after connecting. Client → Server

{
  "op": "auth",
  "bearer": "<jwt>",
  "req_id": "auth-1"
}

Server → Client

{
  "op": "auth",
  "success": true,
  "user_id": "<user_id>",
  "req_id": "auth-1"
}

API Key Authentication

Alternatively, authenticate using an API key. Client → Server

{
  "op": "auth_api_key",
  "api_key": "<api_key>",
  "signature": "<signature>",
  "timestamp_ms": 1731541800000,
  "nonce": "random-unique-string",
  "req_id": "auth-1"
}

The signature must be an Ed25519 signature of:

EKIDEN_WS|AUTH|{timestamp_ms}|{nonce}

After successful authentication, subscribe to private topics.

{
  "op": "subscribe",
  "args": [
    "order",
    "execution",
    "position",
    "account_balance"
  ],
  "req_id": "sub-1"
}

Public market data is available from the public WebSocket without authentication. Common public topics include:

orderbook.<depth>.<symbol>
trade.<symbol>
ticker.<symbol>
kline.<interval>.<symbol>
insurance_pool.<symbol>
adl_alert.<symbol>

5. Typical Trading Flow

A typical market maker integration follows this sequence:

Obtain a JWT or use API Key authentication.
Connect to the public WebSocket.
Subscribe to market data.
Connect to the private WebSocket.
Authenticate the private connection.
Subscribe to private account topics.
Place, amend, or cancel orders using the REST API.
Monitor order, execution, position, and account updates through the private WebSocket.

6. Error Handling

Common HTTP status codes include:

Status	Description
`400`	Invalid request
`401`	Authentication failed
`403`	Permission denied
`404`	Resource not found
`429`	Rate limit exceeded
`500`	Internal server error
`503`	Service temporarily unavailable

Refer to the Error Handling guide for the complete list of application error codes.

7. Rate Limits

REST API requests are subject to rate limits. When a limit is exceeded, the server returns:

HTTP 429 Too Many Requests
Retry-After response header

Clients should respect the Retry-After value before retrying requests. Refer to the Rate Limits guide for current limits.

Overview

Getting Started

Setup

Fund Your Account

Market Data

Trade

Market Make

Account & Portfolio

Access Controls

Troubleshooting

RESTful API

WebSocket Guide

Websoket Reference (AsyncAPI)

Market Maker Integration Guide

1. Overview

Supported Protocols

Environments

2. Authentication

Obtain a JWT

REST Authentication

API Key Authentication

3. REST API

4. WebSocket

JWT Authentication

API Key Authentication

5. Typical Trading Flow

6. Error Handling

7. Rate Limits

​1. Overview

​Supported Protocols

​Environments

​2. Authentication

​Obtain a JWT

​REST Authentication

​API Key Authentication

​3. REST API

​4. WebSocket

​JWT Authentication

​API Key Authentication

​Subscribe

​5. Typical Trading Flow

​6. Error Handling

​7. Rate Limits

1. Overview

Supported Protocols

Environments

2. Authentication

Obtain a JWT

REST Authentication

API Key Authentication

3. REST API

4. WebSocket

JWT Authentication

API Key Authentication

Subscribe

5. Typical Trading Flow

6. Error Handling

7. Rate Limits