FAQ
Please view the following list of frequently asked questions, hopefully it can help you integrate the Golf event centre more efficiently:
Last updated
Was this helpful?
Please view the following list of frequently asked questions, hopefully it can help you integrate the Golf event centre more efficiently:
Last updated
Was this helpful?
We recommend that you first try load a golf tournament in sandbox. First try pull the /tournament endpoint to get an eventID to pass in sandbox. You can then take it a step further and look at the different modules that are available. This will help you understand how the integration library works. Note that before you start, you will need to have an introduction call with the Integration Management team at IMG Arena, they will showcase the sandbox tool and provide you the access/tokens needed to start the integration work.
First you should hit the /tournament endpoint to get a list of tournaments that IMG Arena cover. Remember to pass dateFrom and dateTo to return events against a date range. i.e: return all golf events starting 2022 and ending 2022. https://dde-api.imggaming.com/golf/tournaments?dateFrom=2022-01-01&dateTo=2022-12-31
Once you have this, for a given week that a golf tournament is live, you can connect to /schedule endpoint to get a list of Tee-times. please view the /schedule endpoint for more details.
To map at tournament level, we recommend that you pull the /tournament endpoint and use "name", "tour", "startDate" and apply fuzzy logic parser to map events as the name of the tournament and start date will be universal.
name
Name of the tournament
To retrieve the tournament name related to the ID.
startTeeTime
Returns time of the first tee-off of the tournament
To determine the start time of the tournament. Note that value will populate when the initial tee-times are made available. If tee-times are not available, then Null will be returned.
isStreaming under golfCourses --> roundNo --> holes object
Returns which hole will have streaming enabled
Once the course details are made available, you can use this parameter to determine which hole will have streaming.
id
Unique ID for the tournament
This ID returned will be the "eventID" used in the integration library. i.e this is the event ID needed to load the tournament via the event centre.
tour
Returns the name of the federation of which the golf tournament is apart off.
Helps determine if the tour is apart of PGA, LPGA or DPWT. This will help when it comes to mapping. Note that we return "tour": "European Tour" for DPWT events.
startDate
Returns the start date of the tournament.
This will help with mapping.
--> Static data to build would be:
-Name of the tournament -Start date of the tournament -The unique "id" for the tournament to pass as the "eventID" in the integration library. -Which federation the tour is part off.
startTime
Start time for the group
expected time for when the group will start the hole.
date
Stat date for the group
Start date of the group.
groupId
Unique group ID for the group
You will need to save the groupId if you will be using initial context within the integration library. The GroupID will be useful when trying to link a 3/2 ball on the frontend to the 3/2ball markets. i.e so if a user clicks on a particular group the relevant markets will be displayed and vice versa.
teeSeq
Tee Sequence for a given group. i.e "teeSeq": 4 means 4th group to start on the hole.
This will help you determine the ordering of the groups.
round
The round the tee-times are related to.
This will help determine which round the tee-time is related to.
hole
The hole that the group will start on, either will be 1 or 10
Will inform you which hole the groups are expected to started from.
players within group--> groupNo --> teams--> teamNo
determine which players are within a group.
Will inform you which players are within a group. This will help mapping at group level.
--> The static data to build:
Before you can hit this endpoint, you will need to know the tournament name, tournament ID and expected time for when the initial schedule will be released (i.e normally 2 days before the tournament)
Then you can build grouping information by round: -The groupings for a round, i,e groupId --> who are within the group for a particular round. -When the group are going to start/take their first shot. -Which hole they will start on. Hole 1 or 10. -Order of play for the groups.
Note that initially tee-times/grouping information will be released for rounds 1 and 2. Round 3 and 4 grouping information are released post round 2.
Once the initial tee-times are made available, within the /tournament/{ID} endpoint, we will return "startTeeTime". If we do not have the initial tee-times, when Null will be returned.
Currently the event centre will render when the tee-times are made available.
Most golf tournaments that IMG Arena cover start on a Thursday (Round 1) and finish on a Sunday (Round 4)
The initial schedule is normally received 2 days before a tournament starts (normally Tuesday midday GMT) which will contain the Tee-times/grouping for rounds 1 and 2. The tee times/groups for rounds 3 and 4 will be released once play for day 2 and 3 are complete. We recommend that you pull the schedule endpoint every Tuesday for the upcoming tournament every minute and after player has finished post round 2 and 3.
“startTime” are in UTC format of HH:MMZ. Z will be the offset, if there is an offset it’ll be + or - the amount.
This is up to you. We recommend maybe a few hours after the event has finished. The event centre will display an event 2-3 weeks in the past.
Currently, you will need to view the /leaderboards websocket to retrieve the roundStatuses. This will inform you when a round starts, in-progress, suspended / finished. If you do not have access to this feed, please speak to your dedicated Integration Manager at IMG Arena.
We highly recommend that you get streaming working on sandbox before implementing on your internal systems. We suggest setting up a call with your Integration Manager at IMG Arena to show you how to get this working locally.
There are 2 actions needed to getting streaming working via sandbox.
1) please view our documentation on How to generate the streaming tokens: https://docs.imgarena.com/streaming-integration/authentication/token-creation
Setting up and using the Node.js script on your machine can be the easiest and simplest, i.e: https://docs.imgarena.com/streaming-integration/authentication/token-creation/node.js-token-generator-code
Make a copy of the Token Generator script and save it locally. Note to update your IP address and ALC token within this script.
Once you run this script, if successful, it will return a auth token and a timestamp.
2) Pass these values in the Integration Library with your ALC operator ID.
i.e sandbox example with streaming code:
https://codesandbox.io/s/group-detail-view-only-forked-rfq0li
If you are testing outside golfing hours, note to connect to the weekly simulations. *Link to weekly sim page*
Depending on the commercial and coverage level of a given tournament, IMG Arena would stream a 3-par hole on the first 9 and last 9.
There are 3 ways to go about retrieving this information.
1) You can look directly within the /tournament/{ID} and see if any of the holes returns "isStreaming": true.
This is the most up-to-date and programmatic way to check.
2) You can contact your Integration Manager/Customer solutions team at IMG Arena for a "golf schedule with coverage level" 3) Check the schedule in the ALC platform. please liaise with Integration Managers at IMG for more info.
Due to rights, IMG Arena have 3 different level of coverage. L1 events with the most coverage and L3 events with smaller level of coverage.
L1 = shot by shot data + streaming on 2 par 3 holes
L2 = hole by hole data and no streaming available
L3 = leaderboards only
*note that for LPGA, we only have L2 and L3 coverage. L2 coverage will include the TV world feed.
We recommend that you pull the /tournament endpoint and look at the “ScoringType” returned against the tournament.ScoringType docs: https://docs.imgarena.com/golf-operator-integration-instructions/-LyZmBxEQvjCmOANJop3/static-data/tournament-s-endpoint#scoringtypes
L1 = ShotlinkWithLaser
L2 = ScoredWithWalkingScorer
L3 = HoleScoresOnly
During integration process; please escalate all queries to the Integration/CSM team. Please use the dedicated communication channel.
Once you are live: Please escalate all queries to our support team: support@openbet.com. Our support team are available 365 a year 24/7
For the response time for support:
15 minutes for the first response
15 minutes for the next update
30 minute intervals for any further updates thereafter
We recommend that you use a minimum height of 362px and width of 320px. Reducing the height might misalign text and buttons.
Currently due to broadcasting right; all our streams run 360p (728 Kbps)
Geo-blocking for streaming is carried out at operator level on the IMG Arena side. We suggest speaking to your dedicated Customer Solution Manager for more information on this.
IMG Arena have an endpoint which returns a listing of golfer Ids. Containing; Player ID, Player name, Country, Date of birth (if known), European tour ID and PGA tour ID.
i.e: https://dde-api.imggaming.com/golf/players
Please liaise with your Integration Manager at IMG Arena for more information.
If we return round 401 in the feed, note that this indicated that the tournament went into a play-off stage.
You can customise the golf event centre to match your colour brand guidelines. We highly recommend having a session with our UX team or providing your brand colour guidelines to your dedicated Integration Manager and they will create mockups for you to review. They can provide you a high level document highlighting the possible changes.
In order to pass your GA ID, within the options field in the integration library, please pass userId.
options: { videoPlaybackEnabled: true, userId: UA-XXXXXX-X}
if you require your GA ID, please liaise with the IMG Integrations team.
DPWT release this information 7 days before the tournament starts. PGA send it on a Friday around 5pm ET when the course data is sent
Disabling Favouriting
Allow you to disable the favouriting functionally
Disabling Searching
Allow you to disable the search functionally
Hole map default perspective
Allows the options to choose whether you would like the hole maps to show 2D or 3D by default.
Hole Map icons
Allows you to turn off any of the following icons:
3D toggle
Reset
Full Screen
Green
Leaderboard flags
Gives you the options of choosing whether you would like to show player flags next to their name.
Custom Favorite icon
Gives you the ability to have your own Fav icon.
Group Detail V2
On hole and shots view moves the player selector into the header to release more real estate to the map.
if you require the above feature flags, please liaise with the IMG Arena integrations team.