Create Liveblog from external source
This endpoint is only available for customers who have booked this feature. Please ensure your organization has access before using this API.
Overview
This endpoint allows you to create a liveblog for a sports event using data fetched from an external provider. The API pre-fills the liveblog with match data such as teams, players, and scoreboard information. Additionally, automatic posting of events like goals, cards, or substitutions can be configured.
Endpoint
POST /apigw/sports/v2/{organizationId}/liveblog/createFromExternal
Path Parameters
organizationId(string, required): The ID of your organization.
Request Body
The request body should contain the following fields:
provider(string, required): The name of the external data provider. Only “gn-gsd” (Gracenote) is supported.matchId(string, optional): The ID of the match to fetch from the provider. EithermatchId,phaseIdoroverallIdmust be provided.phaseId(string, optional): The ID of the phase to fetch from the provider. EithermatchId,phaseIdoroverallIdmust be provided.overallId(string, optional): The ID of the overall to fetch from the provider. EithermatchId,phaseIdoroverallIdmust be provided. IfphaseIdandoverallIdare supplied at the same time,phaseIdis preferred.title(string, optional): Custom title for the liveblog. If not provided, a default title will be generated based on the match data.locale(string, optional): The locale for the liveblog content. Defaults to “en”.autoPostEnabled(boolean, optional): Whether automatic posting of match events is enabled.autoPostConfiguration(AutoPostConfiguration, optional): Configuration for automatic posting ifautoPostEnabledis set to true. The configuration can include options to exclude specific events or scoreboards. Everything will be synced if object is missing.
AutoPostConfiguration
excludeScoreboard(boolean, optional): Whether to exclude the scoreboard from automatic posting.excludeEvents(string[], optional): An array of event types to exclude from automatic posting.
Auto Post Configuration Example
If you enable automatic posting, the autoPostConfiguration field can be structured like this:
{
"excludeScoreboard": true,
"excludeEvents": ["soccer.goal"]
}
Provider
Provider: Heimspiel
- ID:
heim - Supported Sport Types:
- soccer
- Supported Events:
soccer.goalsoccer.own-goalsoccer.yellow-cardsoccer.red-cardsoccer.yellow-red-cardsoccer.penalty-kick-missedsoccer.substitutionsoccer.startsoccer.pause-halvessoccer.resume-halvessoccer.end-of-regular-playsoccer.start-overtimesoccer.pause-overtimesoccer.resume-overtimesoccer.end-of-overtimesoccer.start-shootoutsoccer.end
- Scoreboard:
true
- Supported Events:
- soccer
Provider: Gracenote
- ID:
gn-gsd - Supported Sport Types:
- soccer
- Supported Events:
soccer.goalsoccer.yellow-cardsoccer.red-cardsoccer.substitutionsoccer.penalty-kick-missed
- Scoreboard:
true
- Supported Events:
- cycling
- Supported Events: (No events supported yet)
- Scoreboard:
false
- soccer
Responses
Success
- Status:
200 OK - Body: Tik::Model::Game Object
Errors
400 Bad Request: If the request is malformed or required data is missing.422 Unprocessable Entity: If validation of the request data fails (e.g.,matchId,phaseIdandoverallIdare missing).404 Not Found: If the specified route or data source provider is not found.
Example Request
POST /apigw/sports/v2/YOUR_ORGANIZATION_ID/liveblog/createFromExternal
{
"provider": "gn-gsd",
"matchId": "12345",
"locale": "en",
"autoPostEnabled": true
}