Provider review · Pro Kabaddi League match and player-stat features
KabaddiAPI review
KabaddiAPI appears in the Roanuz Sports documentation as a dedicated Kabaddi data product, and its official references show match-detail and player-stat resources for the Pro Kabaddi League. This is a much narrower proposition than a general multi-sport API: it may help an app build a Kabaddi score or player-history view, but only after validating the endpoint and event set. The key editorial distinction is status: public docs are visible, yet the material reviewed does not establish a current stand-alone Kabaddi subscription or production availability.
By Sarah MitchellUpdated
Our verdict
Editorial integration fit: 7.4/10, provisional. Roanuz’s public Kabaddi reference is specific enough to support a useful technical investigation, including match and player-stat routes. It does not provide enough current commercial evidence to recommend assuming a live standalone product. The score reflects the documented specialist shape while discounting the apparent legacy route, lack of verified current plan information and absence of an independently confirmed coverage matrix. Contact the provider before treating the API as available for a new production build.
Key facts
- Provider relationship
- Kabaddi API is listed in the Roanuz Sports family; it is not a separate vendor. [1]
- Match data
- The official match reference describes a Kabaddi match-detail API and shows a Pro Kabaddi example. [1]
- Player data
- The official player-stat reference describes career and season-level statistics. [2]
- Route format
- Documentation examples use a legacy rest.cricketapi.com REST path and access_token query parameter. [1]
Pros and cons
Pros
- The public documentation is sport-specific rather than generic: it names Kabaddi match resources, a competition key and player statistics such as raid and tackle outcomes. That gives a developer a concrete schema to inspect and can support a better requirements discussion than a vague statement that the provider “covers Kabaddi.”
- The same Roanuz family offers cricket and football services. A buyer interested in multiple sports can discuss whether those relationships simplify commercial account management, while still treating each sport’s endpoint and availability as separate until the provider confirms otherwise.
- The player-stat guide distinguishes individual seasons and career-level information. For a Kabaddi history page or a season comparison, those concepts are relevant and provide a useful basis for a prototype if the required player, team and competition identifiers can be obtained.
Cons
- The examples point to a legacy `rest/cricketapi.com/rest/v2/kabaddi` route and an access-token parameter rather than a clearly current, versioned Kabaddi-specific portal. A visible guide may be maintained as documentation but does not prove that an account can still receive credentials or that the route is included in a present plan.
- Public evidence is concentrated on the Pro Kabaddi League and examples rather than a current, exhaustive competition list. Do not infer coverage of all national leagues, international events, seasons or tournaments from one PKL example. Ask for exact competition coverage and historical availability.
- The reviewed official pages do not establish present commercial terms, quotas, supported transport, update guarantees or use rights for Kabaddi. Those gaps matter more than a low price: a team cannot assess production fit until it knows whether the legacy service is actively sold and what support is attached.
Provider website screenshots
A Roanuz sport line, not a standalone company
The Roanuz Sports documentation lists Kabaddi API alongside Cricket and Football offerings. That places KabaddiAPI within the Roanuz family; it should not be treated as an unrelated provider merely because the directory uses its own slug. The distinction is useful for vendor identity and screenshots, but it does not show that all three products share a subscription or current technical stack. Ask the provider to confirm whether the Kabaddi product remains separately available.
The official match reference describes a match-detail API and supplies a Pro Kabaddi example. A related player-stat page documents career and season statistics. Those are substantive clues about the intended product: match context plus a player-history layer. They are not a current API health check, guarantee of support or proof that the same endpoints are available under a newly issued key today.
Sources: [1] Roanuz Sports — Kabaddi Match API, [3] Roanuz Sports — API Coverage guide
A clear example, but an older-looking route
The documentation’s example uses a GET request to a `rest.cricketapi.com/rest/v2/kabaddi` path, with a match key and access token. The route name and token style are important to record because a developer may encounter the same pattern in older tutorials. New integrations should ask whether this is the present supported route, whether a newer version exists, and whether any migration or sunset policy applies.
The player-stat reference describes season and overall statistics, with fields associated with Kabaddi scoring such as raid points, tackle points and success rates. This supports the view that the product aims beyond a fixture list. Before building an analytics model, obtain a current schema and confirm how event scoring corrections, player identity changes and season boundaries are represented. The public page does not establish completeness across the sport’s entire event universe.
Sources: [1] Roanuz Sports — Kabaddi Match API, [2] Roanuz Sports — Kabaddi Player Stats API
Pro Kabaddi examples are not a universal coverage promise
The publicly visible examples are anchored in the Pro Kabaddi League, including a PKL competition key and sample match/player references. That is helpful if the project is explicitly PKL-focused, but it cannot support a claim that all Kabaddi leagues are covered. Ask for an active-season list, exact competition identifiers, historical ranges and a field-level map before presenting the service as a comprehensive Kabaddi source.
Kabaddi products often need more than a scoreboard: raid sequences, player participation, team rosters, points and status changes all affect fantasy and editorial displays. The documentation indicates some player-stat dimensions, but the reviewed pages do not independently verify the full event model or its update rules. Write acceptance criteria around the exact screen being built and require the provider to confirm each piece against a current response.
Sources: [3] Roanuz Sports — API Coverage guide, [1] Roanuz Sports — Kabaddi Match API, [2] Roanuz Sports — Kabaddi Player Stats API
Current access is the unresolved purchasing question
Roanuz maintains public pages that list Kabaddi in its documentation navigation, and the product guide remains reachable. That is evidence that Kabaddi has been documented; it is not enough to assert that the original route is currently sold, that new keys can be issued, or that support is available for a fresh deployment. The review therefore marks the current commercial availability as unconfirmed rather than describing the service as discontinued or guaranteeing access.
Before investing in an adapter, ask Roanuz whether this exact Kabaddi API is active, what current base URL and authentication method should be used, and which plan grants it. Request an explicit answer on request limits, supported competitions, current seasons, historical data, delivery options, caching and commercial display rights. If the vendor points to a replacement or migration, cite that successor separately and preserve the distinction from the documented product.
Sources: [3] Roanuz Sports — API Coverage guide, [1] Roanuz Sports — Kabaddi Match API
A specialist lead that needs a vendor confirmation first
KabaddiAPI is worth investigating when a product is built around PKL scores, player histories or fantasy statistics and the developer can obtain direct confirmation from Roanuz. It is not appropriate to treat a docs page as a purchase-ready reference. A low-risk next step is to ask for a current account, test endpoint and a written league matrix; if the provider cannot confirm access, move to another supplier rather than building against an uncertain legacy route.
The 7.4 score is provisional because the source material offers sport-specific examples but incomplete evidence about current availability. It reflects the potential relevance of the documented match and player concepts, offset by uncertainty around commercial access and modern support. It is neither a negative customer review nor a prediction of service quality. The associated CricketAPI or FootballAPI products are related siblings, not verified successors to KabaddiAPI.
Sources: [1] Roanuz Sports — Kabaddi Match API, [2] Roanuz Sports — Kabaddi Player Stats API, [3] Roanuz Sports — API Coverage guide
Frequently asked questions
Is KabaddiAPI operated by Roanuz?
The official documentation places Kabaddi API within the Roanuz Sports family, alongside the company’s Cricket and Football products. This review therefore identifies it as a Roanuz sport product, while keeping the Kabaddi-specific endpoint and access questions distinct.
Sources: [1] Roanuz Sports — Kabaddi Match API, [3] Roanuz Sports — API Coverage guide
Does the official documentation show a Kabaddi match endpoint?
Yes. The public match reference describes match detail and shows a Pro Kabaddi example using a Kabaddi-specific route. That establishes the documented interface, not current route provisioning, support status or access under a new account.
Is the product currently available to new customers?
Current stand-alone availability is unconfirmed in the public sources reviewed. The documentation remains accessible, but that alone does not prove new credentials are being issued or that the legacy route is included in a current package. Ask Roanuz directly before planning production use.
Sources: [3] Roanuz Sports — API Coverage guide, [1] Roanuz Sports — Kabaddi Match API
Does it cover every Kabaddi league?
The reviewed examples and competition key refer to the Pro Kabaddi League. They do not prove coverage of every national, international or historical competition. Request a current season-by-season coverage list and endpoint-level data map.
Sources: [1] Roanuz Sports — Kabaddi Match API, [3] Roanuz Sports — API Coverage guide
Why is the editorial score provisional?
The 7.4 score reflects useful sport-specific match and player-stat documentation but also an older-looking REST route and missing public evidence about current plan access and production rights. It is an editorial fit assessment, not customer feedback or a service-quality measurement.
Sources: [1] Roanuz Sports — Kabaddi Match API, [2] Roanuz Sports — Kabaddi Player Stats API, [3] Roanuz Sports — API Coverage guide
How our editorial ratings work
KabaddiAPI scores 7.4 out of 10. This is our editorial fit score, not a customer score.
Our scores are subjective website-integration fit assessments based on providers’ publicly described products, not customer-review averages or independent speed, uptime or accuracy tests. We consider publishing usefulness, integration options, documented data scope, access information and clarity of product documentation. A higher score is not a guarantee of suitability. BettorServe is the featured first placement; the remaining list is a curated shortlist, not an exhaustive market ranking.
This is a commercially oriented comparison site. We may earn a commission through eligible partner links, at no extra cost to you. BettorServe is our featured first listing. Commercial relationships and featured placements should be considered alongside the product details, and you should confirm current terms directly with a provider before purchasing.
Sources
Content last reviewed