Table Tennis API Pricing for Live Scores, Rankings, Statistics and WebSocket
Choose a Table Tennis API plan based on the competition coverage, request capacity, historical depth, live data, rankings, statistics, head-to-head access and real-time WebSocket features your application needs.
{
"plan": "PRO",
"monthly_price": "$XX",
"requests": "PLAN_LIMIT",
"live_scores": "included",
"rankings": "included",
"statistics": "included",
"websocket": "PLAN_DEPENDENT"
}
Table Tennis API Plans for Every Stage of Development
Pricing should reflect how your product uses data rather than forcing every customer into the same package. A prototype may need only core fixtures and scores, while a commercial analytics platform may require broader competition coverage, deeper history, rankings, statistics, head-to-head data and real-time streaming.
The plan structure below is designed to be easy to understand and easy to replace with your final commercial terms.
Developer
For testing authentication, endpoint structure and basic table tennis data during early development.
- Core REST API access
- Selected competition coverage
- Fixtures and results
- Basic live score access where supported
- Player profiles
- Documentation access
- Placeholder request quota
- Placeholder rate limit
Starter
For small live-score, ranking, tournament or statistics applications.
- Everything in Developer
- Broader competition coverage
- Live scores where supported
- Set-level match data
- Player rankings
- Basic statistics
- Head-to-head access
- Placeholder request quota
- Placeholder rate limit
Growth
For growing commercial applications that need more data categories, traffic capacity and historical context.
- Everything in Starter
- Expanded competition coverage
- Live score access
- Point-by-point where supported
- Full ranking endpoints
- Player and tournament statistics
- Historical results
- Expanded H2H access
- Placeholder request quota
- Placeholder rate limit
Pro
For high-traffic applications, live products and advanced analytics that require broader access and real-time delivery.
- Everything in Growth
- Higher request capacity
- Broader historical depth
- Point-by-point live data where supported
- Advanced statistics
- Ranking history
- WebSocket access where included
- Priority support tier
- Placeholder connection limit
- Placeholder rate limit
Enterprise
For broadcasters, large platforms, data businesses and custom commercial integrations with higher volume or licensing requirements.
- Custom competition coverage
- Custom request capacity
- Custom WebSocket requirements
- Historical data requirements
- Advanced commercial licensing
- Custom redistribution terms
- Priority technical support
- Custom SLA options
- Custom onboarding
- Custom billing terms
Compare Table Tennis API Plans
Replace placeholder quotas and feature assignments after final pricing is confirmed.
| Feature | Developer | Starter | Growth | Pro | Enterprise |
|---|---|---|---|---|---|
| Monthly price | $XX | $XX | $XX | $XX | Custom |
| Requests | Placeholder | Placeholder | Placeholder | Placeholder | Custom |
| Rate limit | Placeholder | Placeholder | Placeholder | Placeholder | Custom |
| Fixtures | Included | Included | Included | Included | Included |
| Results | Included | Included | Included | Included | Included |
| Live Scores | Selected | Included | Included | Included | Custom |
| Point-by-Point | Plan dependent | Plan dependent | Where supported | Where supported | Custom |
| Player Rankings | Selected | Included | Included | Included | Custom |
| Ranking History | Limited | Limited | Expanded | Expanded | Custom |
| Statistics | Basic | Basic | Expanded | Advanced | Custom |
| Head-to-Head | Selected | Included | Included | Included | Custom |
| Historical Results | Limited | Limited | Expanded | Expanded | Custom |
| WebSocket | Plan dependent | Plan dependent | Optional / dependent | Where included | Custom |
| Odds | Add-on / dependent | Add-on / dependent | Add-on / dependent | Add-on / dependent | Custom |
| Predictions | Add-on / dependent | Add-on / dependent | Add-on / dependent | Add-on / dependent | Custom |
| Support | Standard | Standard | Enhanced | Priority | Custom |
| SLA | Not specified | Not specified | Plan dependent | Plan dependent | Custom |
Table Tennis API Pricing Is Based on More Than Request Count
Competition Coverage
Broader tournament coverage may require a higher plan or custom agreement.
Request Volume
Higher traffic applications need greater monthly and short-term request capacity.
Historical Depth
Deep historical results, rankings and statistics may be priced differently from current data.
Live Data
Real-time score access may have different commercial requirements from fixtures and results.
Point-by-Point Data
Point-level live events may be available only on selected competitions or plans.
WebSocket Connections
Connection count, subscriptions and streaming volume can affect plan requirements.
Odds and Predictions
These products may require separate data sources, licensing or add-ons.
Commercial Rights
Display, storage, redistribution and resale rights may affect enterprise pricing.
Understand Monthly Quotas and Rate Limits
Monthly quotas and short-term rate limits solve different problems and should be displayed separately in final pricing.
| Limit type | What it controls | Example placeholder |
|---|---|---|
| Monthly request quota | Total API requests available during the billing cycle | PLAN_MONTHLY_LIMIT |
| Per-minute limit | Maximum request burst over a short interval | PLAN_PER_MINUTE_LIMIT |
| Concurrent connections | Simultaneous supported WebSocket connections | PLAN_CONNECTION_LIMIT |
| Active subscriptions | Number of live matches or channels subscribed to | PLAN_SUBSCRIPTION_LIMIT |
| Historical export limit | Large archive or bulk-data access | PLAN_EXPORT_POLICY |
Estimate the API Capacity Your Application Needs
Estimate request usage before selecting a plan. The formula depends on whether you poll REST endpoints, use caching or receive live updates through WebSocket.
Illustrative REST Calculation
daily_requests =
active_matches
× requests_per_match
× refresh_cycles_per_match
monthly_requests =
daily_requests
× active_days
Example Planning Scenario
Active matches: YOUR_MATCH_COUNT
Average refresh cycles: YOUR_REFRESH_COUNT
Active days: YOUR_ACTIVE_DAYS
Estimated monthly requests:
YOUR_ESTIMATED_MONTHLY_USAGE
Shared caching can dramatically reduce repeated upstream requests when many users are viewing the same match.
REST API Usage
REST requests are typically used for fixtures, results, rankings, statistics, H2H, historical data and initial live-match state.
Fixtures
Retrieve schedules in batches instead of requesting every fixture separately where possible.
Live Match State
Cache shared live responses to avoid identical requests from every user.
Rankings
Refresh only when a new supported ranking release becomes available.
Statistics
Cache historical statistics and refresh after relevant matches complete.
WebSocket Access May Use Different Limits
WebSocket pricing can depend on connection count, active match subscriptions, event volume or a combination of these factors.
| WebSocket resource | Pricing consideration |
|---|---|
| Concurrent connections | How many upstream connections your account may keep open |
| Match subscriptions | How many matches can be subscribed to simultaneously |
| Tournament subscriptions | Whether tournament-level channels are included |
| Replay access | Whether missed-event replay is supported and included |
| Point-by-point streaming | Whether point-level event delivery is part of the plan |
Historical Data Depth Can Vary by Plan
Historical data can include match results, set scores, ranking snapshots, player statistics and H2H records. The final pricing page should state the available depth by plan.
| Historical feature | Developer | Starter | Growth | Pro | Enterprise |
|---|---|---|---|---|---|
| Match results | Limited | Limited | Expanded | Expanded | Custom |
| Set history | Limited | Limited | Expanded | Expanded | Custom |
| Ranking history | Limited | Limited | Expanded | Expanded | Custom |
| Statistics history | Selected | Selected | Expanded | Advanced | Custom |
| Bulk historical access | No / dependent | No / dependent | Plan dependent | Plan dependent | Custom |
Possible API Add-Ons
Some data products may be sold separately from the core Table Tennis API.
Live Odds
Optional pricing for supported pre-match or in-play markets.
Historical Odds
Optional access to supported historical market snapshots.
Predictions
Optional prediction or probability data where available.
Bulk Historical Export
Custom archive delivery for research or enterprise workloads.
Expanded WebSocket
Additional connection or subscription capacity where supported.
Custom Coverage
Commercial discussion for specific tournaments or data categories.
Choose Monthly or Annual Billing
Monthly Billing
Useful for development, testing, seasonal products and customers who need greater flexibility.
Annual Billing
Suitable for production products that expect to use the API throughout the year.
What Happens When You Reach Your Plan Limit?
The final commercial policy should make quota behaviour explicit so applications do not unexpectedly fail in production.
Hard Limit
Requests stop until the quota resets or the plan is upgraded.
Overage Billing
Additional usage may be billed according to an approved overage rate.
Automatic Upgrade
Accounts may move to a larger plan only if this policy is explicitly supported.
Enterprise Pool
High-volume customers may receive a custom usage arrangement.
Commercial Data Rights Matter as Much as API Access
Customers should know whether their plan permits internal analysis, public display, storage, redistribution or resale.
| Use case | Licensing question |
|---|---|
| Internal analytics | Can data be stored and analysed internally? |
| Public website | Can scores, rankings and statistics be displayed publicly? |
| Mobile application | Can data be distributed to application users? |
| Broadcast product | Are broadcast or media display rights included? |
| Data redistribution | Can raw or derived data be redistributed to customers? |
| Resale | Can access to the underlying data be resold? |
Support Options by Plan
| Support feature | Developer | Starter | Growth | Pro | Enterprise |
|---|---|---|---|---|---|
| Documentation | Included | Included | Included | Included | Included |
| Email support | Standard | Standard | Enhanced | Priority | Custom |
| Integration assistance | Self-service | Self-service | Plan dependent | Plan dependent | Custom |
| Dedicated contact | No | No | Plan dependent | Plan dependent | Custom |
| Custom onboarding | No | No | Plan dependent | Plan dependent | Custom |
Enterprise SLA Options
Service-level commitments should be offered only after uptime, response, incident and support terms have been defined contractually.
Availability Target
Placeholder until the production SLA percentage is approved.
Support Response
Placeholder until severity-based response times are defined.
Incident Communication
Define how customers are informed about major service incidents.
Service Credits
Include only if an approved enterprise contract provides them.
Which Table Tennis API Plan Should You Choose?
Choose Developer If…
You are testing endpoints, building a prototype or validating a product idea.
Choose Starter If…
You are launching a focused live-score, ranking or tournament application.
Choose Growth If…
You need broader competition coverage, statistics, H2H and historical data.
Choose Pro If…
You operate a higher-traffic product or need advanced real-time access.
Choose Enterprise If…
You need custom volume, licensing, coverage, support or SLA terms.
Table Tennis API Pricing FAQs
How much does the Table Tennis API cost?
Final prices have not been inserted on this draft page. Replace the placeholders with approved monthly and annual pricing.
Are live scores included in every plan?
Final plan assignments should be confirmed before launch. Live availability also depends on tournament coverage.
Is point-by-point data included?
Point-level access may depend on both the selected plan and the competition.
Are player rankings included?
Rankings can be assigned to selected plans once the final pricing structure is approved.
Does WebSocket cost extra?
WebSocket can be included in higher plans or sold as an add-on. Final commercial treatment has not yet been specified.
Are odds included?
Odds may require a separate add-on or licence where supported.
Are predictions included?
Prediction data can be priced separately where the product is available.
Can I upgrade later?
The final billing system should allow customers to move to a plan with greater capacity when required.
Do you offer enterprise plans?
Enterprise plans can support custom coverage, volume, licensing, support and service requirements.
Is annual billing available?
The page supports monthly and annual billing presentation, but final annual terms and any discount must still be approved.
Choose the Table Tennis API Plan That Fits Your Product
Compare coverage, live data, rankings, statistics, historical depth, WebSocket access and usage requirements before selecting a production plan.