> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/definitions/states.md). # States A fixture’s `state_id` identifies its current match status. Include `state` to retrieve the state’s code, display name and developer name. ### Get all states ``` GET https://api.sportmonks.com/v3/football/states?api_token={{apiToken}}&per_page=50&page=1 ``` The response checked on 15 October 2026 returned 25 states with `pagination.has_more: false`. The table below reproduces all five fields exactly, including case. Follow response pagination when refreshing the list. ### State reference | id | state | name | short\_name | developer\_name | | -- | --------------------- | ------------------ | ----------- | ------------------------ | | 1 | NS | Not Started | NS | NS | | 2 | INPLAY\_1ST\_HALF | 1st Half | 1st | INPLAY\_1ST\_HALF | | 3 | HT | Half Time | HT | HT | | 4 | BREAK | Break | BRK | BREAK | | 5 | FT | Full Time | FT | FT | | 6 | INPLAY\_ET | Extra Time | et | INPLAY\_ET | | 7 | AET | After Extra Time | AET | AET | | 8 | FT\_PEN | After Penalties | FTP | FT\_PEN | | 9 | INPLAY\_PENALTIES | Penalties | PEN | INPLAY\_PENALTIES | | 10 | POSTPONED | Postponed | POST | POSTPONED | | 11 | SUSPENDED | Suspended | SUSP | SUSPENDED | | 12 | CANCELLED | Cancelled | CANC | CANCELLED | | 13 | TBA | To Be Announced | TBA | TBA | | 14 | WO | Walk Over | WO | WO | | 15 | ABANDONED | Abandoned | ABAN | ABANDONED | | 16 | DELAYED | Delayed | DELA | DELAYED | | 17 | AWARDED | Awarded | AWAR | AWARDED | | 18 | INTERRUPTED | Interrupted | INT | INTERRUPTED | | 19 | AWAITING\_UPDATES | Awaiting Updates | AU | AWAITING\_UPDATES | | 20 | DELETED | Deleted | DEL | DELETED | | 21 | EXTRA\_TIME\_BREAK | Extra Time - Break | ETB | EXTRA\_TIME\_BREAK | | 22 | INPLAY\_2ND\_HALF | 2nd Half | 2nd | INPLAY\_2ND\_HALF | | 23 | INPLAY\_ET\_2ND\_HALF | ET - 2nd Half | 2et | INPLAY\_ET\_SECOND\_HALF | | 25 | PEN\_BREAK | Penalties - Break | PENB | PEN\_BREAK | | 26 | PENDING | Pending | PEN | PENDING | ### Choose the right field * `id`: match this to the fixture’s `state_id` and use it for state filters. * `state`: the API state code, such as `INPLAY_1ST_HALF` or `POSTPONED`. * `name`: the readable status name. * `short_name`: a compact display label. It is not unique: both Penalties (9) and Pending (26) use `PEN`. Do not use it as an identifier. * `developer_name`: a separate API field. Do not derive it from `state`: state 23 returns `INPLAY_ET_2ND_HALF` as its state and `INPLAY_ET_SECOND_HALF` as its developer name. ### Filter by state ID For actively playing phases, use IDs 2, 22, 6, 23 and 9: both regulation halves, both extra-time halves and penalties. Breaks and interruptions are separate states. ``` GET https://api.sportmonks.com/v3/football/fixtures?api_token={{apiToken}}&include=state&filters=fixtureStates:2,22,6,23,9 ``` For postponed or cancelled fixtures: ``` GET https://api.sportmonks.com/v3/football/fixtures?api_token={{apiToken}}&include=state&filters=fixtureStates:10,12 ``` IDs 5, 7 and 8 identify Full Time, After Extra Time and After Penalties respectively. A state label is not a guarantee that a fixture will never receive a later update; handle schedule changes, data corrections and further competition phases in your application. See the [States include tutorial](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/states) for request examples, match-phase handling and display guidance. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sportmonks.com/v3/definitions/states.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.