List Reload Schedules
Lists Warehouse Native experiments, gates or holdouts that have a scheduled reload hour, one entityType per request, sorted by id . Each item shows its sched…
Lists Warehouse Native experiments, gates or holdouts that have a scheduled reload hour, one entityType per request, sorted by id. Each item shows its schedule and whether the scheduler selects it.
eligible is true when the scheduler's rules select the entity. It doesn't guarantee a reload runs. The scheduler can still skip an eligible entity at run time, and skipReasons doesn't report these skips: a scheduled reload already ran that UTC day, scheduled reloads are paused for the project, a gate rule is at 0% or 100%, or a gate rule is inside its real-time auto-reload window.
To change many schedules, collect every id first, then send the PATCH requests. Changing schedules while you page can skip rows, because each change moves entities in or out of the filtered list.
List requests don't count toward the Console API write limit. Each PATCH does: by default, 1,800 writes per 15 minutes and 30 writes per 10 seconds per project, shared by every key and every Console API write.
https://statsigapi.net/console/v1/reload_schedulesAuthorizations
STATSIG-API-KEYstringrequiredapiKey (header)
Query parameters
limitintegerResults per page
10stringnumberpageintegerPage number
1stringnumberentityTypestringrequiredType of entity to list. Each request lists one type.
experimentgateholdoutexperimenteligiblestringWhen true, returns only entities the scheduler selects (eligible: true). When omitted or false, returns every entity with a scheduled reload hour.
truefalsehourintegerReturns only entities scheduled at this UTC hour, from 0 to 23.
0Response
application/jsonmessagestringrequiredA simple string explaining the result of the operation.
dataobject[]requiredShow child attributes
entityTypestringrequiredType of the entity, matching the entityType you requested.
experimentgateholdoutidstringrequiredID to use with /console/v1/experiments/{id}, /console/v1/gates/{id} or /console/v1/holdouts/{id}.
namestringrequiredDisplay name.
scheduledReloadHourintegerrequiredUTC hour, from 0 to 23, at which scheduled reloads start.
format: int64scheduledReloadDaysinteger[]requiredDays of the week with scheduled reloads, from 0 to 6, where 0 is Sunday. null means every day. An empty list means no day, so the entity never reloads (no_days).
nullablescheduledReloadTypestringrequiredReload type for scheduled reloads. An unset type reads as incremental.
fullincrementalturboModebooleanrequiredWhether scheduled reloads use Turbo mode. null means unset, so scheduled reloads keep the latest reload's setting. For experiments, an organization that enforces Turbo mode overrides this value.
nullableeligiblebooleanrequiredtrue when the scheduler's rules select this entity, so skipReasons is empty. The scheduler can still skip it at run time.
skipReasonsstring[]requiredEach scheduler rule this entity fails. Every type: no_days (scheduledReloadDays is an empty list). Gates and holdouts: disabled, archived, no_partial_rollout (no rule passes between 0% and 100%). Experiments: not_started, launched, analysis_ended (the analysis end time has passed), cloud_results (Statsig Cloud computes this experiment's results), incremental_with_secondary_id (incremental reloads don't support a secondary ID type; send scheduledReloadType: "full").
paginationobjectrequiredPagination metadata for checking if there is next page for example.
Show child attributes
itemsPerPagenumberrequiredformat: doublepageNumbernumberrequiredformat: doublenextPagestringrequirednullablepreviousPagestringrequirednullabletotalItemsnumberformat: doubleallstringstatusintegerrequired400messagestringrequiredstatusintegerrequired401messagestringrequiredWas this helpful?
For AI agents: a documentation index is available at /llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.