> For the complete documentation index, see [llms.txt](https://developer.aiodds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.aiodds.com/bookmaker-odds/status-code-overview.md). # Status Code Overview AiOdds uses status codes to describe match progress, period-level states, technical statistics, and language options across API responses and WebSocket payloads. These codes help your system interpret the current state of an event, understand which stage of play is active, map statistical fields correctly, and request or display translated content. ### Status code categories AiOdds status codes are grouped into four main categories: #### Match Status Match Status represents the overall state of a match. Use Match Status when you need to determine whether a match has not started, is currently live, has finished, or is unavailable because of postponement, cancellation, interruption, abandonment, or lost coverage. #### Period Status Period Status describes the current phase or segment of a match. Unlike Match Status, which describes the whole match lifecycle, Period Status provides more detailed information about the active stage of play. This may include halves, quarters, sets, innings, maps, overtime, penalties, breaks, suspensions, walkovers, retirements, and other sport-specific states. #### Technical Statistics Technical Statistics codes identify the type of statistic returned in match score or event-related data. These codes allow your system to map numerical statistic IDs to readable labels such as goals, red cards, yellow cards, corner kicks, shots, possession, kills, towers, and other sport-specific metrics. #### Language Language codes identify supported translation languages in AiOdds. Use these codes when working with translated sports, tournaments, teams, markets, outcomes, or other localized names. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.aiodds.com/bookmaker-odds/status-code-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.