These endpoints require the Player Entity ID, NOT the Team ID. Using a Team ID (e.g., 275923 for Alcaraz) on /api/players/ endpoints will return incorrect data. You must use the Player Entity ID (e.g., 3111 for Alcaraz).
Player sport validation is enforced. If you use a non-tennis player ID, the API will return an error indicating the player’s actual sport (e.g., “Player 3111 is not a tennis player (sport: football)”). This prevents cross-sport data leakage.
How to find the Player Entity ID:
Search for the player → GET /api/search?q=alcaraz → returns Team ID 275923
Get team details → GET /api/teams/275923 → response contains "player": { "id": 3111, ... }
Use player.id for all /api/players/ endpoints → GET /api/players/3111/h2h/119248
Both IDs represent the same person but access different data. Use /api/players/:id for career stats and H2H. Use /api/teams/:id for match history and tournament entries.
# Use Player Entity IDs for both players (NOT Team IDs)curl -X GET "https://v2.tennis.sportsapipro.com/api/players/3111/h2h/119248" \ -H "x-api-key: YOUR_API_KEY"
