README.md

Live Sports Data API Documentation

This documentation set explains how to call the Live Sports Data API endpoints that live under the /api/livescores path. Use it to build requests and understand response shapes.

• The full OpenAPI spec lives at flashscore/flashscore_openapi.yaml.
• Start with request essentials for base URL, auth headers, defaults, errors, and response formats.

Documentation map

• Request essentials - base URL, defaults, errors, and response formats.
• Feeds and scoreboards - raw feeds and sport scoreboards.
• Feed naming patterns - common feed name patterns for /feed.
• Navigation and categories - navigation, categories, and tournament lists.
• Tournaments - fixtures, results, tables, and tournament metadata.
• Matches - match detail endpoints.
• Participants - team and participant resources.
• Players - player profiles and stats tables.
• Rankings - ranking discovery and tables.
• News - news lists and articles.
• Search - search and suggestions.
• Updates and system - updates and status.
• GraphQL and odds hashes - hash-based query endpoints.
• Media and assets - banners, stats, and images.
• Schemas - response object shapes.
• Sport IDs - known sportId values.

Example request

curl "https://live-sports-data-api.p.rapidapi.com/api/livescores/sports/1/scoreboard?dayOffset=0&lang=en"

Common flow:

1. Call a scoreboard endpoint and read sharedindexes_event_id from records[].fields.
2. Use that eventId with match detail endpoints (see Matches).