Get Scheduled Order
Use Case
Retrieve a single scheduled order by ID. The response returns the schedule under data.schedule with its current state, cadence, next execution time, and cumulative execution stats (total_executions, total_amount_spent, total_quantity_acquired).
Path Parameters
Scheduled order identifier from Create Scheduled Order.
Response Fields
Top-level flag indicating the schedule was retrieved.
Human-readable status message.
The schedule record. Fields mirror Create Scheduled Order's response plus cumulative execution stats.
Schedule identifier.
Company that owns the schedule.
Asset being acquired on each tick (e.g. 'BTC').
Currency used to fund each tick (e.g. 'USDT').
Per-tick spend in the smallest unit of quote_currency.
'daily', 'weekly', or 'monthly'.
0–6 (Sunday=0) when frequency is 'weekly'; 0 otherwise.
1–31 when frequency is 'monthly'; 0 otherwise.
24-hour HH:MM firing time in UTC.
'active', 'paused', 'cancelled', or 'completed'.
Next scheduled run. Null when status is terminal.
Timestamp of the most recent execution. Empty string when the schedule has never fired.
Number of ticks that have fired.
Cumulative quote_currency spent across all executions.
Cumulative currency acquired across all executions.
When the schedule was created.
When the schedule was last modified.
Client-supplied idempotency key.
Unique request identifier for support and tracing.
Server time when the response was generated.