Rankings are a tennis-unique feature — not available in the football or basketball APIs. These endpoints return comprehensive ranking data including rank, points, and player details.
Rankings return Team IDs — that’s the only ID you need for tennis on V2. In V2 tennis the team entity is the player; pass the returned ID directly to /api/teams/:id, /api/teams/:id/events/last/:page, /api/teams/:id/near-events, /api/teams/:id/featured-event, /api/teams/:id/media, and /api/teams/:id/tournament/:tid/season/:sid/statistics. The separate /api/players/:id career family is not currently available for tennis — see the Team/Player docs for the supported surface.
Use this endpoint (/api/rankings/wta) for WTA Singles. The legacy ranking type 6 is known-broken upstream (ranks start at 101 instead of 1) and should not be called directly. /api/rankings/wta is now backed by the correct upstream source and returns rank #1 through #500 as expected.
The ranking type ID. Valid tennis types: 5 (ATP alt), 7 (ATP Singles), 8 (WTA Singles), 34 (ATP Race), 35 (WTA Race alt). Type 6 is accepted for back-compat but is broken upstream — use /api/rankings/wta for WTA Singles instead.
Non-tennis type IDs will return a 400 Bad Request with an error message listing the valid types. This prevents football or other sport data from leaking through the tennis namespace.
