Fixture Changes Endpoint

XML example

<fixture>
<scheduled_start_time_changes>
<scheduled_start_time_change old_time="2018-03-23T11:00:00+00:00" new_time="2018-09-07T10:00:00+00:00" changed_at="2018-03-14T00:07:23+00:00"/>
</scheduled_start_time_changes>
</fixture>

Endpoint Parameters

You can customize the endpoint response by using the following parameters.

Parameter

Description

Possible Values

language

Required

Language code for translation.

See all supported languages and their codes on language support

afterDateTime

Optional

the datetime after which you want the fixture changes. The endpoint returns all the fixture changes from such a date onwards (till the timing of the call).

ISODate format (YYYY-MM-DDThh:mm:ss).

E.g: 2023-05-29T12:05:00

sportId

Optional

The id of the sport you want the fixture changes for.

Format - sr:sport:{id}

E.g: sr:sport:1

Endpoint Structure

The main elements and sub-elements provided by the Fixture endpoints are the ones shown in the list below:

  • <fixture_changes>

    • <fixture_change>

Attributes Explained

The following attributes are found in the fixture change element.

Name

Description

sport_event_id

the unique id assigned to the sport event by SR

update_time

the date and time when the fixture is updated/changed

Last updated

Was this helpful?