API Update: Changes to History Endpoints and Parameter Clarifications

We are committed to continuously improving the performance and reliability of the Delta Exchange API. As part of these efforts, we are announcing several updates regarding pagination and parameter handling for our REST API endpoints.

1. Changes to Order and Fills History APIs

We are implementing updates to the GET /v2/orders/history (Order History) and GET /v2/fills (User Fills) endpoints. These changes focus on optimizing data retrieval through our cursor-based pagination system.

• Removal of 'total' Field (Live Now): The total field has been removed from the pagination metadata (meta) for these endpoints. Going forward, the response metadata will focus on providing the before and after cursors necessary to navigate results efficiently.

• Reduced Maximum Page Size (Tentative: 28th January 2026): We are planning to update the maximum allowed page_size for these history endpoints to 50.

  • Requests with a page_size value higher than 50 will only return a maximum of 50 items.

  • This measure helps prevent excessive load and ensures faster response times for all traders.

2. Updated Parameter Descriptions for Product IDs and Symbols

To provide better clarity on how to query multiple products, we have updated the descriptions for parameters involving product IDs and ticker symbols.

• Format Clarification: Parameters such as product_ids, symbols, and underlying_asset_symbols must be formatted as comma-separated strings.

• New Maximum Limit: Requests are now restricted to a maximum of 10 Product IDs or symbols per API call.

• Affected API Endpoints:

  • Tickers: GET /v2/tickers (including filtering by underlying_asset_symbols).

  • Orders: GET /v2/orders (Active Orders).

  • Positions: GET /v2/positions/margined (Margined Positions).

  • History & Fills: GET /v2/orders/history and GET /v2/fills.

Action Required

Traders using high page_size values (e.g., the previous default of 100 for some endpoints) or attempting to fetch more than 10 products in a single request should update their integration logic to accommodate these new limits.

Please note that while pagination cursors remain the standard for fetching large datasets, the removal of the total field encourages a more dynamic, cursor-following approach to data fetching.

Attempting to fetch more than 10 products in a single request should update their integration logic to accommodate these new limits. 

Note: By default, if the product_ids parameter is not provided, these APIs return data for all products.

For further technical details, please refer to the latest Delta Exchange API documentation.