Submit a LIVE or HISTORICAL run for a version of the strategy
Enqueues a run for a version of the strategy. The run is LIVE when as_of_date is omitted or equals today (UTC), else HISTORICAL. LIVE submissions write the per-version pipeline trigger; HISTORICAL ones are rate-limited (weekly/monthly credits) and use the DB-poll path.
Authorizations
Enter 'Bearer' followed by a space and then your JWT or API Key.
Example: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
or Bearer YOUR_API_KEY_HERE
Path Parameters
UUID of the strategy
Body
Parameters for submitting a strategy run.
The as-of date for the run (YYYY-MM-DD). Omitted or today (UTC) -> LIVE; a past date -> HISTORICAL. Future dates are rejected (400).
Request factsheet generation for the resulting run.
Re-run even if a completed run already exists for this version/date.
Batch-queue priority for HISTORICAL scheduling (1-10).
1 <= x <= 10The version to run. Defaults to the version matching the strategy's current draft (created if needed) and promoted to active.
Response
Submission accepted; the submitted version with its run state (id + status/completed/has_factsheet). Poll /versions/{id} for progress.
A saved version of a strategy plus its run state. In rollup mode (no as_of_date) latest_run_date and runs_count are populated; in date-scoped mode (as_of_date supplied) as_of_date is echoed and the rollup-only fields are null.
The normalized objective snapshot for this version.
Whether this version is the strategy's active version.
Raw run status code (e.g. 1 pending, 100 done, negative failed).
The version's id (verbose; pairs with strategy_id, no bare id).
Echoed when date-scoped; absent/null in rollup mode.
The version's latest completed run date; null when date-scoped.
Total runs for the version; null when date-scoped.