Get Football Round Details
View all Football Data API endpoints →Request one round's detail using an identifier discovered from a league's rounds listing. Requires roundid; no leagueid, season or date parameter is declared. The response has not been verified, and the catalogue example '1' is not proof of a globally valid round identifier. Inspect identity and grouping before caching a round across competitions; obtain a real ID from the preceding rounds-list read.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/football/get-rounds-detail-by-round-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/football/get-rounds-detail-by-round-id?key=<API_KEY>&roundid=<roundid>'
Query Result
Use Cases
- Create a round page after resolving a genuine ID from the selected league's rounds list.
- Validate the relationship between a chosen round and its competition before linking navigation.
- Test whether cache keys need league context to avoid cross-competition round collisions.
- Inspect round-detail structure before selecting fields for a matchweek summary.
Frequently asked questions
Can I enter a matchweek number directly as roundid?
Do not guess. Discover a genuine ID from the league rounds list; the catalogue example 1 is not proof of universal validity.
Does round detail always return every match in that round?
The content and grouping have not been demonstrated. Inspect them before treating the response as a complete fixture list.
Is caching by roundid alone safe?
Verify identifier scope first and retain league context if collisions are possible. The request itself declares no leagueid or season input.