WebSocket connections use the same API key authentication and signing path as before. Only the hostname changes for the dedicated Trade API path.
- For connection and subscription examples, see Quick Start: WebSockets.
- For all REST and WebSocket base URLs, see API Environments and Endpoints.
- For lower-latency
fillanduser_ordersupdates, see Fill and order updates. - To generate clients or inspect channel payloads directly, download the AsyncAPI specification.
- For detailed CF Benchmarks channel usage (
cfbenchmarks_value), see CF Benchmarks Value Feed. - For real-time Pyth prices (
pyth_value), see Pyth Value Feed.
Forward compatibility
A channel can gain new message types, and a message new fields. Ignore any messagetype or field your client doesn’t recognize instead of treating it as an error.