Instrument Status Updates
Instrument Status Updates
Both endpoints support the same pagination pattern (since, cursor, limit) and can be filtered by event_symbol for efficient parallel loading.
Lifecycle States vs Market Status
- Lifecycle states represent the instrument's position in its overall lifecycle (e.g., Active, Suspended, Closed). Use this to determine if an instrument can potentially be traded or has reached end-of-life.
- Market status indicates whether the instrument is currently open for trading. An instrument may be in an Active lifecycle state but have a Closed market status.
Parallel Loading by Event
For efficient data loading, fetch status updates per event in parallel:
# For each event, fetch lifecycle and market status in parallel
GET /dcm/v1/public/get-instrument-lifecycle-states?event_symbol={event_symbol}&since={last_updated_time}
GET /dcm/v1/public/get-instrument-market-status?event_symbol={event_symbol}&since={last_updated_time}
Since instruments within the same event typically change state around the same time (e.g., when a game ends), filtering by event_symbol enables effective parallelism across events.
📄️ public/get-instrument-lifecycle-states
Returns a paginated list of instrument lifecycle state changes. Use this endpoint to track when instruments transition between states (e.g., from `Suspended` to `Closed`).
📄️ public/get-instrument-market-status
Returns a paginated list of instrument market status changes. Use this endpoint to track when instruments become available or unavailable for trading.