StatsHub Docs
APIEndpoint referenceBasketball

/basketball/event/{id}/player-odds

Bookmaker labels are matched to players with namematch.LabelMatcher rather than the Fuse.js scan the original used.

GET
/api/basketball/event/{id}/player-odds

Bookmaker labels are matched to players with namematch.LabelMatcher rather than the Fuse.js scan the original used. Fuse's Bitap score has no equivalent here and reproducing it would be guesswork; the tiered matcher is stricter, and requires exactly one candidate at each tier. The failure it prevents — attaching a line to the wrong player — is worse than showing no line, which is the only way the two differ.

Path Parameters

id*string

Query Parameters

statType?string
teamId?string

Response Body

application/json

application/json

application/json

curl -X GET "https://example.com/api/basketball/event/string/player-odds"
{  "data": {    "property1": null,    "property2": null  }}

/basketball/event/{id} GET

The body is the joined row itself, not wrapped in `data`.

/basketball/events/by-date GET

The guard is `if (!startOfDay && !endOfDay)` — an and, not an or — so supplying just one of the two passes validation and the missing one becomes NaN in the where clause, which is a 500.