Skip to main content
Prefer Streaming for Real-Time UpdatesThis polling API is subject to rate limits. For production applications that need continuous order and trade updates, use the gRPC Order Stream instead. The streaming API provides real-time execution reports as they happen.

​
Endpoints

Participant context required for Trade StatsPOST /v1/report/trades/stats (GetTradeStats) accepts Auth0 JWT with read:reports at the gateway, but still requires participant context downstream (x-participant-id / DCM participant context). Market-data-only clients without a participant receive 401. This route is not supported for MD-only access today, and there is no public/retail substitute.read:reports alone is not enough. Other report endpoints (orders search, trades search, etc.) also require participant context.

​
When to Use

Streaming First ArchitectureFor any use case requiring real-time order or trade updates, use the streaming API. Use the REST Report API only for:
  • Historical data queries
  • One-time lookups
  • Batch exports for reporting

​
Search vs Export

  • Search endpoints (/v1/report/orders/search, /v1/report/trades/search, /v1/report/executions/search): Return paginated JSON results for programmatic access
  • Export endpoints (/v1/report/orders/csv, /v1/report/trades/csv, /v1/report/executions/csv): Return CSV file streams for spreadsheet analysis and reporting

​
Common Filters

See the individual endpoint documentation for complete filter options.