use the 202 status consistently in triggering endpoints #2224

Open

nhoening wants to merge 3 commits into

mainfrom

feat/api/use-202-status-consistenly-in-triggering-and-fetching-endpoints

Commits on Jun 5, 2026

use the 202 status consistently in triggering endpoints (forecasting, scheduling) and provide follow-up URLs in the response
nhoening
committed
let get_schedule endpoint use status 202 as well, if jobs are not finished (just like get_forecast) - for now only use this (over the old 400 code) if API_SUNSET is being used
nhoening
committed

Commits on Jun 18, 2026

Merge branch 'main' into feat/api/use-202-status-consistenly-in-triggering-and-fetching-endpoints
nhoening
authored