Match State Platform Schedule API

1 Introduction
2 Authenticating against Genius Sports APIs
3 Obtaining Fixture Id
4 Schedule Info schema

Introduction

Schedule API receives and exposes information about scheduled fixtures that will be covered for specific source of sports events data.

Authenticating against Genius Sports APIs

In order to access Genius Sports Match State Platform APIs or Match Statistics API, see Authenticating against Genius Sports APIs.

Obtaining Fixture Id

In order to request a fixture Id you need to query schedule API /GET endpoint (UAT endpoint)

We would recommend using V2 option, though the data returned is the same as V1.

Mandatory parameters that needs to be entered:

sourceId
sportId
from (date)
to (date)

** Interval between from and to needs to be <= 7 days

Example:

{{url}}/api/{{version}}/sources/{{sourceId}}/sports/{{sportid}}/schedule?to=2022-06-25T20:26:26.13&from=2022-06-20T00:22:37.155901

The schedule info response will be array of fixtures covered with that source within the specified timeframe:

[
    {
        "timeRaisedUtc": "2022-06-14T10:33:00.939748",
        "lineups": "Unknown",
        "startDateUtc": "2022-06-25T14:00:00",
        "fixtureId": "91160028",
        "origin": "Tv",
        "status": "Covered"
    },
]

Schedule Info schema

[
  {	
		"timeRaisedUtc": "string,"
		"lineups": "string",    // Unknown|True|False
		"startDateItc": "string,"
		"fixtureId": "string",  // Genius Sports Fixture Id
		"status": "string", 	// Unknown|Covered|Cancelled|NotCovered
		"origin": "string",  	// Unknown|Tv|Venue|Server
		
  }
]

timeRaisedUtc - points time of update
lineups - points if a fixture will have lineups data
startDateItc - points the fixture start time
fixtureId - points unique Genius Sports Fixture Id
status - points if fixtures is covered or cancelled or not covered
origin - points the type of coverage

Cancelled is used for Fixtures that have been abandoned/postponed, as well as for edge cases where the game was played sooner than initially scheduled and our live team did not know in time to cover the event.

NotCovered is used for Fixtures where for any reason we will not be able to continue with the coverage.

Fixtures that we never intend to cover will not be visible in the API.