TESTNET
Markets
Trade
Lending Vaults
More
User Docs Developer Docs Sdk API Docs Help
Welcome to Polyester
Concepts
Overview
Creating an Account
Authentication Methods
Turnkey
Smart Wallets
Dashboard
Account Security
MFA
Asset Lifecycle
Supported Assets
Deposit Funds
Withdraw Funds
Transfer Funds
Inventory and Supply
Overview
Trading Fees
Base vs Quote
Lending Fees
Withdrawal Fees
Liquidation Fees
Rebates
Overview
On-chain Visibility
Overview
Supplying
Borrowing
Collateral
Interest
Liquidations
Overview
Trades
Candles
Order Book
Data Delivery
Notifications
Appearance
Localization
Sound Effects
Overview
Architecture
Benchmarks
Matching Engine
Settlement
Safeguards
Overview
Validators
Gas Abstraction
Layer-1 Benchmarks
Audits
Read Pre-compiles
Create Invite Code
Managing Links/Codes
Claiming Rewards
Auto-Convert Rewards
Overview
Create/Delete subaccounts
Permissions
Roles
Audit Logs
Unified Trading Account
Spot Trading
Order Types
Tools
Privacy
Custom Layouts
Overview
Asset Wrapping
Vaults
Zipper Security
What Is TEE?
  1. Market Data
  2. /
  3. Data Delivery

Data Delivery

Polyester market data is available through multiple delivery surfaces (the trading UI, REST, WebSocket, and FIX protocol), all drawing from the same underlying market state.


Delivery Surfaces

User interface (UI)

The Polyester website itself is a primary delivery surface for market data.

Prices, order books, trades, and candles displayed in the UI are driven by live market feeds and update continuously as market activity occurs. While the interface is optimized for interaction and visualization rather than programmatic access, it consumes the same underlying data sources that power external delivery methods. This ensures consistency between what users see in the interface and what is available through APIs.

REST

REST endpoints provide request–response access to market data.

Well suited for:

  • Bots that poll for updates
  • Systems that need historical or snapshot-style data
  • Integrations that prioritize simplicity and reliability

All market data exposed through advanced interfaces is also available via REST, with the exception of certain high-frequency feeds that may be restricted.


WebSocket

WebSocket streams provide real-time, push-based access to live market updates.

Well suited for:

  • Live trading interfaces
  • Latency-sensitive consumers
  • Applications that need continuous updates without polling

Streaming data is available in both JSON and Protobuf formats, allowing consumers to balance ease of use with performance.


ConnectRPC (advanced)

ConnectRPC provides a typed, protocol-based interface primarily intended for SDKs, internal tooling, and advanced users.

It exposes the same underlying data as REST and WebSocket, with stronger typing and tighter integration for supported environments.

Use of ConnectRPC is optional and not required to access market data.

Consistency Across Interfaces
Trades, candles, and order book data remain consistent across REST, WebSocket, and advanced interfaces. Differences between delivery methods relate to how data is accessed, not what data exists.

Order-Level Data Access

Certain high-resolution data, such as order-level (L3) feeds, may be subject to access controls or delivery constraints.

Availability and eligibility for these feeds depend on market participation and platform policies, and may vary by delivery surface.

Details on L3 access and qualification are covered in the Order Book documentation.


Choosing a Delivery Method

Most users will interact with market data through the UI or REST endpoints.

Users building real-time systems or custom interfaces typically rely on WebSocket streams, while advanced users and SDK developers may choose ConnectRPC for deeper integration.


Developer Documentation

Refer to the Developer Documentation for:

  • Endpoint listings
  • Connection details
  • Authentication
  • Rate limits
  • Schemas and examples
Previous

Order Book

Next

Notifications

  • Delivery Surfaces
  • User interface (UI)
  • REST
  • WebSocket
  • ConnectRPC (advanced)
  • Order-Level Data Access
  • Choosing a Delivery Method
  • Developer Documentation