history-payload-validator

OpenAlgo history API requests fail with 400 errors when required fields like symbol, exchange, interval, start_date, or end_date are missing. Validating the payload beforehand ensures these fields are present and properly formatted to prevent failed runs.

Run a validation pass against your history endpoint to check that required fields are present, normalize date ranges, and sanitize values. This precheck prevents invalid data from reaching the API and stops execution errors before dispatch.

OpenAlgo history validation supports legacy fields like resolution and from/to as applicable. It enforces the standard required fields first, while allowing optional legacy parameters to maintain compatibility with older payload structures.

History payload validation applies across NSE, NFO, and MCX workflows. It prechecks the master contracts for the target exchange and symbol, refreshing them if needed, to ensure data requests are valid before execution.

Missing data fields in OpenAlgo history requests are caused by incomplete payloads or outdated master contracts. Validating required fields and prechecking master contracts for the target exchange resolves these gaps before the API call is made.

Invalid interval errors occur when the interval field in the history payload is missing or incorrectly formatted. Field sanitization during payload validation normalizes the format and catches invalid values before the request is dispatched.