Site
Home / Forum / Developers / API Proposal: Enhancing Match Events Granularity (Penalties & Red Cards Detail)
Home / Forum / Developers / API Proposal: Enhancing Match Events Granularity (Penalties & Red Cards Detail)
API Proposal: Enhancing Match Events Granularity (Penalties & Red Cards Detail) |
| Posted: 11 Mar 2026 20:52 | |||
Posts: 5 Joined: 2025 | Dear TheSportsDB Team and Admin, I am writing to you as an independent developer currently building football applications (PWAs) integrated with Cloud Firestore and real-time data tracking. First, I want to thank you for the incredible work you do; your API is a cornerstone for many of us in the sports dev community. However, after extensive testing with match timelines, I’ve identified a key area where TheSportsDB can evolve to compete with "Elite" data providers like ESPN or Opta: Event Granularity. The Problem: Currently, when a critical event occurs (like a penalty or a red card), the data sent via the API is often too generic. Receiving just "Goal - Penalty" or "Red Card" lacks the narrative depth that modern sports apps require. The Proposal: I suggest standardizing specific sub-types for these events within the strTimelineDetail or strComment fields: Penalty Specificity: Differentiate the cause (e.g., Handball, Foul/Trip, or VAR overturn). Red Card Context: Specify if it was for "Last Man Foul," "Violent Conduct," or "Second Yellow." Player Involvement: Identifying not just the scorer, but the player who committed the infraction (e.g., "Penalty awarded for handball by [Player Name]"). Why this benefits TheSportsDB: Competitive Edge: Most mid-tier APIs fail at this level of detail. By offering structured "Why" data, you become the go-to source for professional-grade storytelling and Fantasy apps. Ecosystem Growth: As developers, we can build more immersive UIs. A notification saying "Penalty for handball" is far more engaging than just "Penalty." When our apps look professional, it reflects directly on the quality of your data. Data Integrity: Moving towards this "ESPN-level" detail transforms the database from a simple log into a powerful analytical tool. I am more than willing to discuss how we could structure these JSON fields to keep them lightweight yet informative for the community. Let's keep raising the bar for digital football together! Best regards, Ing. Luis Larez Independent Developer & AI Lab Researcher e-mail: [email protected] | ||
 | |||
| Posted: 14 Mar 2026 14:02 | |||
 zag Posts: 3,933 Joined: 2020 | Good idea, but we simply don't get that data at the moment from our upstream source sorry. I'd love to improve it though in the future. | ||
|