Skip to main content
POST
Compute and ingest Reg SHO SSR restrictions from price

Body

application/json

Request body for POST /api/internal/ssr/compute.

If the caller supplies at least one of start_date/end_date, the other field left None defaults independently to most_recent_trading_day - 7d / most_recent_trading_day respectively.

When BOTH are None (the daily-timer call, and the common case) the endpoint instead self-heals from reg_sho_ssr_ingest_watermark: it resumes the day after the last successfully completed compute_ssr run's processed_through watermark, falling back to the same 7-day trailing window only if no watermark exists yet. This means a skipped run (deploy window, outage) gets picked back up automatically on the next daily call instead of silently leaving a hole beyond 7 days -- see trigger_ssr_compute.

start_date
string<date> | null

Inclusive start date.

end_date
string<date> | null

Inclusive end date.

Response

Successful Response

Response from POST /api/internal/ssr/compute.

rows_inserted
integer
required
start
string<date>
required
end
string<date>
required