Tick Size Updates

Trade with greater precision using the Paxos APIs.

To enable tighter spreads for assets trading at sub-dollar and sub-penny levels, we're increasing tick size across the platform for select and new assets. This is not a breaking change. Starting August 24, 2022, we're updating the Polygon (MATIC) tick size (decimal precision) for REST, FIX and WebSocket APIs. Integration testing in sandbox begins August 4, 2022.

• See FAQ: Markets & Orders for more information on all supported markets.

Testing Timeline

The changes are scheduled to be deployed in the sandbox environment on August 4, 2022, giving you additional time to prepare and test your integrations. Once our testing is complete, we plan on going live in production no earlier than August 24, 2022.

We recommend you test your integrations in sandbox during the three-week testing window to ensure that all REST and WebSocket integrations support strings with six ticks, 0.000001 (1e-6), for all current and future assets, and that FIX integrations support strings with 19 decimal places, 0.0000000000000000001 (1e-19).

If you run into any problems or have additional questions, please contact support.

What's Changing in the Paxos v2 REST API?

Parameters for the Orders and Quotes endpoints are changing. While this is not expected to be a breaking change, minimally, your integrations must support a tick size of 0.0001 (1e-4) for MATIC. We recommend that all integrations support six ticks, 0.000001 (1e-6), for all current and future assets.

If you run into any problems or have additional questions, please contact support.

Request Parameter Tick-size Changes

When creating orders, thequote_amountparameter tick size remains at 0.01 (1e-2).

Response Parameter Tick-size Changes

Thevolume_weighted_average_priceremains at eight ticks: 0.00000001 (1e-8). Tick sizes for Pricing endpoint responses remain the same.

What's Changing in the FIX API?

Ideally, your FIX integrations should support up to 19 decimal places, 0.0000000000000000001 (1e-19), for all assets. Minimally, you your integrations must support 17 decimal places, 0.00000000000000001 (1e-17), for MATIC.

If you run into any problems or have additional questions, please contact support.

What's Changing with WebSockets?

Market data responses will have increased tick-size precision. While this is not expected to be a breaking change, minimally, your integrations must support the increased precision for MATIC to 0.0001 (e-4). We recommend that all WebSocket integrations support tick sizes of six ticks, 0.000001 (1e-6), for all current and future assets.

What's Changing in the ItBit REST API?

NOTICE: itBit REST API End of Life Notification

Paxos will discontinue service for all itBit REST Production and Sandbox APIs on February 22, 2023. After a review of our existing product offerings, we determined that the Paxos REST API (v2) provides a better experience for all users and should be used as the primary entry point for all REST services.

Beginning August 15, 2022, all itBit REST API endpoints are deprecated, initiating a 90-day window for transitioning to the Paxos REST API (v2). To help with the transition, we’ve put together Migrating from itBit (v1) to Paxos (v2) API. The guide provides suggestions on implementing similar functionality using the Paxos REST API (v2).

If you have any questions, contact connectivity@paxos.com.

Market data responses will have increased tick-size precision. While this is not expected to be a breaking change, minimally, your integrations must support the increased precision for MATIC to 0.0001 (e-4). We recommend that all REST integrations support tick sizes of six ticks, 0.000001 (1e-6), for all current and future assets.

If you run into any problems or have additional questions, please contact support.