# OnFixtureChange

This messages will be responsible in updating the status of the fixture.

*MessageType: onfixturechange*

Here is a sample JSON payload on what you should expect to receive on your end:

<details>

<summary>Sample payload</summary>

```
{
    "sportId": 20,
    "fixtureSpecifier": "sr:match:48591917",
    "changeTypeId": 101,
    "changeTypeName": "Other",
    "fixtureStatusId": 4,
    "fixtureStatusName": "Closed",
    "timeStampSent": 0,
    "timeStampReceived": 0,
    "raw": null
}
```

</details>

Properties:

| Name              | Type   | Description                                                                                                                                                   |
| ----------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| sportId           | int    | Unique id of a sport.                                                                                                                                         |
| fixtureSpecifier  | string | Unique id of the fixture.                                                                                                                                     |
| changeTypeId      | int    | <p>Reason why the match status was changed.<br><br>See <a href="/pages/6qxpjsI0gFPeYZgO8h1m#fixture-change-type">Fixture Change Type</a> for more details</p> |
| changeTypeName    | string | <p>Reason why the match was closed.<br><br>See <a href="/pages/6qxpjsI0gFPeYZgO8h1m#fixture-change-type">Fixture Change Type</a> for more details</p>         |
| fixtureStatusId   | int    | <p>The current status of the fixture.<br><br>See <a href="/pages/6qxpjsI0gFPeYZgO8h1m#fixture-status">Fixture Status</a> for more details.</p>                |
| fixtureStatusName | string | <p>The current status of the fixture.<br><br>See <a href="/pages/6qxpjsI0gFPeYZgO8h1m#fixture-status">Fixture Status</a> for more details.</p>                |
| timeStampSent     | long   | epoch timestamp on when the message was sent by the provider                                                                                                  |
| timeStampReceived | long   | epoch timestamp on when our service received the message from the provider                                                                                    |


---

# Agent Instructions: 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:

```
GET https://flyingcockatoo.gitbook.io/odds-feed-documentation/odds-feed-integration/message-types/onfixturechange.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.