Audience: developers and agents scheduling market-aware jobs.
Coverage and source scope
Use this route before scheduling a market-data job or interpreting a missing daily observation. It returns a bounded calendar window for one supported market and identifies whether each row uses configured-holiday or weekend-only coverage.sessionStatus is a schedule, not evidence that trading occurred or that an exchange did not change its hours. Preserve coverage, confidence, statusNote, and row-level provenance when a workflow depends on the result. See API conventions.
Canonical metadata
datasupportedMarketscoverageconfidencestatusNoteper-row provenancerequestId
Example request
Example response
Session coverage
Start withmarket, start, and duration when a job needs a known exchange calendar. The response is capped at 31 consecutive dates and is not paginated. configured_holidays means the response includes the configured local holiday calendar; weekend_only means weekday exchange-holiday closures may be absent and an open row can be tentative. supportedMarkets reports the coverage posture for each listed market. See freshness and trust.
Errors
Invalidstart values return a contract-aware request error. Do not substitute an unsupported market code with an assumed exchange calendar: the route defaults unsupported codes to XNYS.
Give this prompt to your agent
Failure posture
- preserve market, date, coverage, confidence, statusNote, provenance, and requestId with a scheduled job
- treat weekend-only coverage as a calendar aid, not an exchange-authoritative holiday feed
- do not infer a trading session from an absent date outside the requested window

