AsyncAPI channel · One Trading · One Trading WebSocket Streams API

/

Single multiplexed WebSocket connection. Clients send AUTHENTICATE and SUBSCRIBE control messages and receive market-data and (once authenticated) private trading events. All messages carry a "type" discriminator.

Open source AsyncAPI → All One Trading channels One Trading provider profile
Provider: One Trading AsyncAPI: v2.6.0 Spec: One Trading WebSocket Streams API Operations: 2 Messages: 23

Channel address

/

Operations

publish
sendCommands
Messages the client sends to the server.
receiveEvents
Messages the server sends to the client.

Messages

AUTHENTICATE
Authenticate the connection with an API token (Trade permission required).
Content-Type:
SUBSCRIBE
Subscribe to one or more channels for a set of instruments.
Content-Type:
PING
Keep-alive ping; server replies with PONG.
Content-Type:
CREATE_ORDER
Create an order over the WebSocket connection.
Content-Type:
CANCEL_ALL_ORDERS
Content-Type:
CANCEL_ORDER
Content-Type:
CANCEL_ORDER_BY_CLIENT_ID
Content-Type:
MOVE_ORDER
Move (reprice) an existing order.
Content-Type:
MARGIN_UPDATE
Update margin on a futures position.
Content-Type:
AUTHENTICATED
Authentication succeeded.
Content-Type:
ORDER_BOOK_SNAPSHOT
Full order book snapshot for a subscribed instrument.
Content-Type:
ORDER_BOOK_UPDATE
Incremental order book update.
Content-Type:
PRICE_TICK
Trade price tick for a subscribed instrument.
Content-Type:
BOOK_TICK
Best bid/ask (top-of-book) update.
Content-Type:
ORDER_BOOKED
An order was accepted and booked.
Content-Type:
ORDER_REJECTED
An order was rejected.
Content-Type:
ORDER_CLOSED
An order was closed/cancelled.
Content-Type:
ORDER_FULLY_FILLED
An order was fully filled.
Content-Type:
TRADE_EXECUTED
A trade was executed against one of the client's orders.
Content-Type:
SETTLEMENT
A futures settlement event.
Content-Type:
FUNDING_PAYMENT
A futures funding payment was applied.
Content-Type:
BALANCE_ADJUSTMENT
An account balance was adjusted.
Content-Type:
ERROR
Error envelope; carries a single machine-readable code.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/untitled"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.