Frequently Asked Questions

What are the benefits of Table tennis on the IMGA Multisport platform?

Enhanced Efficiency: The multisport platform offers improved data management and distribution efficiency. Clients can enjoy faster access to data updates and reduce the time and resources required for data integration and maintenance.

Consistency and Standardisation: Our multisport environment ensures a standardised data schema for table tennis in line with other sports like soccer, basketball, snooker, volleyball and more. This consistency simplifies data processing, reporting, and analysis, providing more accurate and reliable insights.

More Data Points: We now have additional aggregated statistics for point started, played, point lets and also cards which weren't previously available.

Future-Proofing: Clients are positioning themselves for the future by migrating to the multisport platform. As the platform continues to evolve, customers can benefit from new features, data enhancements, and additional sports offerings, all within the same environment.

One-Stop Solution: Technical clients can now rely on a single platform to access data for multiple sports, including table tennis as well as volleyball, basketball, soccer or snooker. This consolidates their data sources, making it easier to manage and opens up possibilities for expanding their sports offerings in the future.

Improved User Experience: Clients can provide their users with a more seamless and comprehensive volleyball experience thanks to the unified data feed. This can lead to increased user engagement and satisfaction.

What data points are going to be included for Table Tennis?

A: See here for all action types.

When will the Table Tennis service cease to exist on the legacy DDE Feed and Schema and migrate to the new Multisport platform?

A: Table Tennis is available on our multisport platform today (in the same schema format as other sports), so you can begin integrating that right away.

We are targeting shutting off the legacy feed by the End of Q4 2025

How do we know who served first?

A: We don’t currently send a “first server” field (like the old firstServer in the legacy feed). What we do provide: every Point Scored action (fixtureActionTypeId=1102) tells you which team scored, and every package includes the live score. That gives you the match flow, but not the official first server.

How do we know which team called a timeout and when it is over?

A: Right now, timeout actions don’t include a teamId. There’s no dedicated “timeout over” action. The best way is to look for the next Point Started action (1101) — that’s when play resumes.

What happens if a match ends for irregular reasons?

A: In the endMatch action (id: 5), the metadata called reason will contain one of the following: -Walkover -Injury -Retirement -Disqualifications

How to determine match winner?

A: In the fixture summary attached to the endMatch action, there are fields called homeTeamScore and AwayTeamScore

Which fixture actions types can be deleted?

A: There are 2 scenarios when action types can be deleted:

1. Undo point - creates a delete action for the last pointScored

2. Undo penalty point - creates a delete action for last penaltyPoint

How should we deal with Data corrections?

A: Given all our fastpath betting data is collected in venue by humans, there is a risk of real-time corrections being made given that human error can occur. We have added a sendType value within the /actions websocket to denote the following:

1 Pending (possible action packet) 2 Updated (updates info on confirmed packets) 3 Cancelled (invalidates pending packet) 4 Deleted (deletes confirmed packets) 5 Confirmed (confirmed packet and can be added).