Skip to main content
The ISV gateway exposes sports reference data - players, teams, logos, colors, records, and provider mappings - that complement the exchange-level Reference Data.

​
Players Endpoint

Fetch player reference data directly for player props, combos, and provider ID mapping, without loading an event. This is a public endpoint and requires no authentication. It remains supported at v1 and is not deprecated; there is no standalone v2 players lookup endpoint. Player information embedded in /v2/events complements this endpoint.

​
Query Parameters

Use dotted, camelCase query parameter names. For array filters, repeat the parameter for each value, for example filters.id=781&filters.id=15877.
Provider lookup uses only filters.provider, filters.providerPlayerId, and filters.league. It ignores limit, offset, filters.id, filters.teamId, filters.name, and filters.abbreviation, and returns results sorted by internal player ID. For list mode, leave filters.provider unset; filters.providerPlayerId and filters.league then have no effect.

​
Examples

List players:
Look up a specific player by internal ID. The response still contains a players array; there is no public /v1/sports/players/{id} route.
List players on a team:
Resolve a provider’s player ID to an internal player record:

​
Response Fields

The response is an object containing a players array. No matches return HTTP 200 with {"players": []}. There is no total count or next-page token; in list mode, request subsequent offsets until a page contains fewer players than the requested limit. Each player includes the following fields when available. Internal player and team IDs are serialized as JSON strings because they are protobuf int64 values; provider IDs are strings in the provider’s own namespace. These are player reference records. A returned player does not imply that player has an active prop market or an eligible combo leg; use event and market data to discover those markets.

​
Teams Endpoint

Returns team data for a given series. Use the filters.league parameter to specify the series, which corresponds to the event_series value in instrument metadata (e.g., nfl, nba, nhl, mlb, mls, cbb, cfb).

​
Query Parameters

​
Examples by Series

Substitute the series value in filters.league to get teams for different leagues:

​
Response Fields

Each team object includes:

​
Events Endpoint

Returns active events for a given league.

​
Query Parameters

​
Examples by League

​
When Sports Markets Use Subjects Instead of Teams

Teams are used for standard game markets (moneylines, spreads, totals) where two teams are competing in a specific game. In these cases, team data is attached directly to the event as participants. However, non-championship futures markets for sports — such as MVP awards, season win totals, and other prop futures that aren’t tied to a specific game outcome — use subjects instead of teams. Subjects represent the individual player, team, or entity that the futures market is about.