Growing Discord community — direct access to the developer, live coverage & picks. Join now →
1
Bug Archived Apr 11, 2026 · aamtini

Missing 'player' identifier in /player-stats/ endpoint when filtering by event

Hi, I have found a critical bug in the /api/player-stats/ endpoint. When searching for statistics for a specific match using the 'event' filter (e.g., /api/player-stats/?event=985), the API returns the correct number of statistical records, but it COMPLETELY OMITS the player identifier field (the 'player' field is missing from the JSON results). The response includes fields like fouls, goals, and rating, but there is no player ID or object to identify who the stats belong to. This makes the endpoint unusable for match synchronization. Steps to reproduce: 1. Call GET /api/player-stats/?event=985 (or any other valid event ID). 2. Inspect the results array. 3. Observe that the 'player' field is not present in any record. Please restore the player identifier field as soon as possible. Thank you!

Resolution: Added player field to PlayerStatSerializer
Comments (3)
BSD Support AI Admin AI Apr 11, 2026 22:16
Hi aamtini, Thank you for the detailed report — this does sound like a genuine issue worth investigating immediately. The player field should always be present in /api/player-stats/ responses, regardless of the filter used. Its absence when querying by ?event= specifically suggests this could be a serializer-level bug triggered by that particular filter path, rather than a data problem. A couple of quick things to verify on your end while we investigate: - Try fetching a single record directly (e.g., /api/player-stats/{id}/) to confirm whether the player field appears there. - Check if the field is missing across all event IDs or only specific ones. This is being flagged for our backend team to review the ?event= filter serialization logic. We'll update you as soon as we have a resolution. Sorry for the disruption — appreciate you flagging it clearly!
BSD Team Admin Apr 11, 2026 22:19
Hi aamtini, thanks for reporting this! The player field was missing from the serializer. Fixed — the /api/player-stats/ endpoint now includes a player object with id, api_id, name, short_name, position, and team for every record. The fix is live now.
aamtini Apr 11, 2026 22:38
Wow, that was quick! Thanks for fixing it. Best regards