Table of Contents

TBD

The TBD acronym stands for To Be Decided, which means that represents a competitor which cannot be determined at first e.g. Like when there is a draw and there will be semifinal for sure but you still don’t know who are the competitors which will compete in the semifinal.

A TBD competitor can be proposed through the Fixtures API v2 on endpoint /v2/competitors/tbds

A TBD competitor will be considered as duplicate if there is another with the same combination of name and Sport

A TBD competitor can be requested through the Fixtures API v2 on endpoint /v2/competitors/tbds.

When to use

The TBD competitor can be used when, for some reason, it is unclear who are the competitors which will compete in specific fixture.

How to use

The TBD competitor entity can be used by getting its GSS Id from the Fixtures API v2 on endpoint /v2/competitors/tbds. And then set the needed GSS Id to the request which is going to be made to Fixtures API v2 when it is needed.

Example workflow

1. GET GSS TDBs from Fixtures API v2

   curl --location --request GET 'https://ci.fixtures.api.geniussports.com/v2/competitors/tbds' \ --header 'x-api-key: <<api_key>>' \ --header 'Content-Type: application/json' \ --header 'Authorization: <<id_token>>' \ --data-raw ''

   A successful response would be with status code 200 and JSON data in format:

   { "page": 0, "pageSize": 0, "totalItems": 0, "items": [ { "id": 0, // GSS TBD Id "createdOn": "2022-06-23T10:49:49.608Z", // When was the TBD competitor created "modifiedOn": "2022-06-23T10:49:49.608Z", // When was the TBD competitor last modified "updatesCount": 0, // How many times the TBD competitor was modified "metadataProperties": [ // Sport specific additional data for the TBD competitor (if available) { "name": "string", "value": "string", "isDeleted": true } ], "name": "string", // The name of the TBD competitor "sport": { "id": 0, // GSS Sport Id defines in which Fixtures, Rounds, Seasons the TBD competitor can take part "name": "string", "ref": "/sports/{id}" // Endpoint on which Sport is available }, "genderType": "string", // Defines in which Fixtures, Rounds, Seasons the TBD competitor can take part "locality": { "id": 0, // The TBD competitor's location "name": "string", "ref": "/localities/{id}" // Endpoint on which the Locality is available }, "competitorStatusType": "string", // Defines whether the TBD competitor is active, retired, or unattached } ], "self": "string", "previous": "string", "next": "string", "first": "string", "last": "string" }

    

2. POST Fixture with any of the retrieved GSS TBD competitor Ids:

   curl --location --request POST 'https://ci.fixtures.api.geniussports.com/v2/fixtures' \ --header 'x-api-key: <<api_key>>' \ --header 'Content-Type: application/json' \ --header 'Authorization: <<id_token>>' \ --data-raw '{ "seasonId": 0, "competitors": [ // Include separated by coma 2 GSS TBDs Ids which are going to compete in the Fixture // e.g. 1, 2 ], "startDate": "2021-11-29T09:34:10.302Z", "roundId": 0, "venueId": 0,// GSS Venue Id from previous request "localityId": 0, "name": "string" } '

Read Data Points

Create/Update Data Points

Validations