Get Football Match Status
View all Football Data API endpoints →Request the status read for one event ID to inspect the match states available for application-owned refresh logic. Requires eventid. No response sample has been verified for this status-specific operation. Validate its actual state fields independently of the started and finished flags seen in match details. Handle unknown, missing and cancelled states explicitly rather than assuming a fixed enumeration or guaranteed live delivery.
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-match-event-status-by-event-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/football/get-match-event-status-by-event-id?key=<API_KEY>&eventid=5868072'
Query Result
Use Cases
- Build a match-status refresh worker that records the raw returned state before applying application labels.
- Pause refreshes for events confirmed complete under a verified state mapping.
- Test how a match page displays an unknown or unavailable status without claiming the match was cancelled.
- Investigate status disagreements between this read and a match-detail snapshot.
Frequently asked questions
Which identifier selects a match status?
Use the confirmed match ID from search or fixtures as eventid, not a team or league identifier.
Can I assume started and finished are always returned?
No. Those flags appeared in other demonstrated reads, but this dedicated status payload needs independent field and state-value verification.
Should an unknown state be displayed as cancelled?
No. Keep unknown, missing, cancelled and finished states distinct and retain raw values for investigation. This read does not guarantee live delivery.