Badminton data reference
Generated from GET /v2/sports/29. Not hand-maintained - if the API adds a status or renames a statistic, this page follows on the next build.
- Sport id
- 29
- Participants
- 2
- Match clock
- no
- Incident positions
- no
Statuses 26
Every value event.status_id can take for this sport. Map onto this list rather than parsing status_type: ids are stable, labels are localized, and postponed matches keep status_type: scheduled.
| id | Name | Short | Type | Notes |
|---|---|---|---|---|
| 1 | Not started | Sched. | scheduled | clock stoppedset by incident 427 |
| 6 | Start delayed | Delay. | scheduled | clock stoppedset by incident 438 |
| 5 | Postponed | Post. | scheduled | clock stoppedset by incident 440TRAP: status_type is scheduled, exactly like a normal upcoming match. A postponed match is indistinguishable from a scheduled one unless you look at status_id. Never branch only on status_type. |
| 18 | Live | live | live | |
| 134 | 1st set | 1st set | live | clock running |
| 155 | Break after 1st set | 1st set break | live | breakclock stopped |
| 65 | 2nd set | 2nd set | live | clock running |
| 156 | Break after 2nd set | 2nd set break | live | breakclock stopped |
| 135 | 3rd set | 3rd set | live | clock running |
| 157 | Break after 3rd set | 3rd set break | live | breakclock stopped |
| 136 | 4th set | 4th set | live | clock running |
| 158 | Break after 4th set | 4th set break | live | breakclock stopped |
| 137 | 5th set | 5th set | live | clock running |
| 159 | Break after 5th set | 5th set break | live | breakclock stopped |
| 162 | 6th set | 6th set | live | |
| 160 | Break after 6th set | 6th set break | live | |
| 163 | 7th set | 7th set | live | |
| 161 | Break after 7th set | 7th set break | live | |
| 9 | Halftime | HT | live | clock stoppedset by incident 445Clock is stopped. clock_time holds the value it had at the whistle, so do not render it as running. |
| 2 | Interrupted | Interr. | interrupted | clock stoppedset by incident 441Play stopped and may resume. Incident 1001 (Match resumed) brings it back. Distinct from Abandoned (7), which may never resume. |
| 7 | Abandoned | Abd. | interrupted | clock stoppedset by incident 442Play stopped and may never resume. Same status_type as Interrupted (2), so tell them apart by status_id. |
| 11 | Finished | Fin. | finished | clock stoppedset by incident 437One of FIVE terminal statuses (11, 12, 13, 14, 140). Treat every status_type: finished as terminal - checking for 11 alone misses matches decided in extra time, on penalties or in overtime. |
| 12 | Finished awarded win | AW | finished | clock stoppedset by incident 436Walkover: the result was awarded, not played out. Statistics and the timeline may be empty or not reflect play. |
| 76 | Retired | Ret. | finished | |
| 3 | Cancelled | Canc. | cancelled | clock stoppedset by incident 439 |
| 152 | To finish | To fin. | scheduled | clock stoppedset by incident 451TRAP: status_type is scheduled, but the match already started and was stopped - it is waiting to be finished on another date. Do not present it as an upcoming fixture. |
Results 17
Entries that can appear in participants[].results[], keyed by id. There is no score field - you select the result you need.
| id | Name | Code | Type | Data type |
|---|---|---|---|---|
| 411 | Winner | winner | team | binary |
| 412 | Progress | progress | team | binary |
| 2 | Result | result | team | integer |
| 43 | First set | first_set | team | integer |
| 43 | First set | first_set | person | integer |
| 44 | Second set | second_set | team | integer |
| 44 | Second set | second_set | person | integer |
| 45 | Third set | third_set | team | integer |
| 45 | Third set | third_set | person | integer |
| 46 | Fourth set | fourth_set | team | integer |
| 46 | Fourth set | fourth_set | person | integer |
| 47 | Fifth set | fifth_set | team | integer |
| 47 | Fifth set | fifth_set | person | integer |
| 417 | Sixth set | sixth_set | team | integer |
| 417 | Sixth set | sixth_set | person | integer |
| 418 | Seventh set | seventh_set | team | integer |
| 418 | Seventh set | seventh_set | person | integer |
Event details 9
Per-match metadata in the event's details, with the input type and allowed values.
| id | Name | Code | Input | Data type |
|---|---|---|---|---|
| 1 | First set start date | first_set_start_date | datetime | - |
| 2 | Second set start date | second_set_start_date | datetime | - |
| 3 | Third set start date | third_set_start_date | datetime | - |
| 4 | Fourth set start date | fourth_set_start_date | datetime | - |
| 5 | Fifth set start date | fifth_set_start_date | datetime | - |
| 62 | Sixth set start date | sixth_set_start_date | datetime | - |
| 63 | Seventh set start date | seventh_set_start_date | datetime | - |
| 7 | Sets number | sets_number | select | - |
| 64 | Scoring system | scoring_system | select | - |
Incidents 83
Incident types that can appear in this sport's events_incidents. category: emergency marks operational notices, not match events - never render them on a timeline.
| id | Name | Code | Type | Trader | Category | Notes |
|---|---|---|---|---|---|---|
| 925 | In progress | in-progress | event | no | standard | |
| 2846 | The match will not be covered | the-match-will-not-be-covered | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match will not be covered at all. The attribute gives the reason. Nothing further will arrive.Other: Scout's technical issues, Change of venue, Change of match date, Problems with TV transmission source |
| 902 | 1st set started | set-1 | event | yes | standard | |
| 2847 | Problems with the source of the broadcast | problems-with-the-source-of-the-broadcas | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The broadcast source has a problem. Paired with 2848 when it is solved. |
| 903 | 2nd set started | set-2 | event | yes | standard | |
| 2848 | Problem with the source of the broadcast has been solved | problem-with-the-source-of-the-broadcast | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The broadcast source problem is solved. |
| 904 | 3rd set started | set-3 | event | yes | standard | |
| 2849 | Change of coverage from venue to TV | change-of-coverage-from-venue-to-tv | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. It tells you the coverage SOURCE changed, which usually changes latency and can change how complete the statistics are. Never render it on a timeline. Before kick-off (group: prematch): moved from venue to TV. |
| 905 | 4th set started | set-4 | event | yes | standard | |
| 2850 | Change of coverage from TV to venue | change-of-coverage-from-tv-to-venue | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. It tells you the coverage SOURCE changed, which usually changes latency and can change how complete the statistics are. Never render it on a timeline. Before kick-off (group: prematch): moved from TV to venue. |
| 906 | 5th set started | set-5 | event | yes | standard | |
| 2851 | Change of coverage latency | change-of-coverage-latency | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. It tells you the coverage SOURCE changed, which usually changes latency and can change how complete the statistics are. Never render it on a timeline. Latency of the coverage changed. Relevant if you gate markets on feed delay.Other: from 3-6 to 7-15, from 7-15 to 3-6 |
| 907 | 6th set started | set-6 | event | yes | standard | |
| 2852 | Scouting coverage can start with a delay of | scouting-coverage-can-start-with-a-delay | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Scouting coverage will start late. The attribute gives the size (under 3, 3-5 or 5-10 minutes).Other: < 3min, 3-5 min, 5-10 min |
| 908 | 7th set started | set-7 | event | yes | standard | |
| 2853 | Expected delay in the start of the match | expected-delay-in-the-start-of-the-match | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match will start late. The attribute gives the reason - a team arriving late, problems in the stands and so on.Other: Delayed arrival of a team, Problems in the stands, Referee problems, Infrastructure problems, Weather conditions |
| 2854 | Team line-ups will not be available | team-line-ups-will-not-be-available | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Line-ups will not be available for this match. Do not wait for lineups[] to fill. |
| 922 | Change side | change-side | event | no | standard | |
| 2855 | Source of the coverage is delayed | source-of-the-coverage-is-delayed | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The coverage source is delayed. The attribute gives the size of the delay (about 5 to 20 seconds).Other: ~5sec, ~10sec, ~15sec, ~20sec, ~25sec, ~30sec, >30sec |
| 909 | Set break | set-break | event | no | standard | |
| 2856 | The current part of the game has started with a delay | the-current-part-of-the-game-has-started | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The current period started late. |
| 915 | Abandoned | abandoned | event | yes | standard | |
| 2857 | Verification of result in progress | verification-of-result-in-progress | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 916 | Cancelled | cancelled | event | yes | standard | |
| 2858 | Verification of result completed and correct | verification-of-result-completed-and-cor | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of the result finished. Values are confirmed. |
| 912 | Finished regular time | finished | event | yes | standard | |
| 2859 | Verification of key statistics is in progress | verification-of-key-statistics-is-in-pro | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 913 | Interrupted | interrupted | event | yes | standard | |
| 2860 | Verification of key statistics completed and correct | verification-of-key-statistics-completed | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of key statistics finished. Values are confirmed. |
| 914 | Postponed | postponed | event | yes | standard | |
| 2861 | Verification of game clock is in progress | verification-of-game-clock-is-in-progres | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 919 | Retired | retired | event | yes | standard | |
| 2862 | Verification of game clock completed and correct | verification-of-game-clock-completed-and | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of the game clock finished. Values are confirmed. |
| 901 | Start delayed | start-delayed | event | yes | standard | |
| 2863 | Match coverage interrupted due to technical issues | match-coverage-interrupted-due-to-techni | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Coverage stopped because of technical issues. 2864 or 2865 says whether it comes back. |
| 917 | To finish | to-finish | event | yes | standard | |
| 2864 | Match coverage will continue | match-coverage-will-continue | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Coverage will continue after the interruption. |
| 920 | Technical timeout | technical-timeout | event | no | standard | |
| 2865 | Match coverage will not continue | match-coverage-will-not-continue | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Coverage will NOT continue. Expect no further incidents for this match. |
| 911 | Finished awarded win | finished-aw | event | yes | standard | |
| 2866 | The match is abandoned | the-match-is-abandoned | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match was abandoned. The attribute gives the reason.Other: Problems in the stands, Referee problems, Infrastructure problems, Serious player injury, Weather conditions |
| 2867 | Waiting for official decision regarding match resumption | waiting-for-official-decision-regarding- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Waiting for an official decision on whether the match resumes. 2868 or 2869 follows. |
| 2868 | Match will resume shortly | match-will-resume-shortly | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match resumes shortly. |
| 2869 | Match will not resume | match-will-not-resume | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match will not resume. |
| 2870 | Expected delay in the start of the next part of the game | expected-delay-in-the-start-of-the-next- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The next period will start late. The attribute gives the reason.Other: Problems in the stands, Referee problems, Infrastructure problems, Weather conditions |
| 2871 | Change of coverage from venue to TV | change-of-coverage-from-venue-to-tv-live | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. It tells you the coverage SOURCE changed, which usually changes latency and can change how complete the statistics are. Never render it on a timeline. During play (group: live): moved from venue to TV. |
| 2872 | Change of coverage from TV to venue | change-of-coverage-from-tv-to-venue-live | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. It tells you the coverage SOURCE changed, which usually changes latency and can change how complete the statistics are. Never render it on a timeline. During play (group: live): moved from TV to venue. |
| 2873 | Change of coverage latency | change-of-coverage-latency-live | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Coverage latency changed. The attribute gives the direction, for example from 3-6 to 7-15 seconds. Relevant if you gate markets on feed delay.Other: from 3-6 to 7-15, from 7-15 to 3-6 |
| 2874 | Expected delay in the start of the match - safety reasons | expected-delay-in-the-start-of-the-match | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The match will start late for safety reasons. |
| 2875 | Verification of key statistics is in progress | verification-of-key-statistics-is-in-pro | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 2876 | Verification of key statistics completed and correct | verification-of-key-statistics-completed | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of key statistics, after the match finished. Values are confirmed. |
| 2877 | Verification of player names for key incidents in progress | verification-of-names-for-key-incidents- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 2878 | Verification of player names for key incidents completed and correct | verification-of-names-for-key-incidents- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of player names on key incidents finished. Values are confirmed. |
| 2879 | Verification of result is in progress | verification-of-result-is-in-progress | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 2880 | Verification of result completed and correct | verification-of-result-completed-and-cor | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. Verification of the result, after the match finished. Values are confirmed. |
| 2881 | Problems with the low latency source of the coverage | problems-with-the-low-latency-source-of- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The low-latency source has a problem. Paired with 2882. |
| 2882 | Problems with the low latency source of coverage has been solved | problems-with-the-low-latency-source-of- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. The low-latency source problem is solved. |
| 2883 | Player name verification is in progress - substitution | player-name-verification-is-in-progress- | event | yes | emergency | emergencyOperational notice, not a match event - category: emergency. Never render it on a timeline. A verification started. Whatever it covers may still change - hold off on caching it. |
| 1000 | Betstart | betstart | event | yes | standard | marketBetting markets may be activated. Other: Master |
| 1010 | Betstop | betstop | event | yes | standard | marketAll betting markets are closed: a goal, penalty or red card looks likely, or the situation on the pitch is unclear. Other: Master |
| 1001 | Match resumed | match-resumed | event | yes | standard | informingUsed when an interrupted match resumes. |
| 1200 | Technical problems | technical-problems | event | yes | standard | marketTechnical problems during coverage. Closes all match markets automatically. |
| 931 | Point | point | team | yes | standard | |
| 928 | Serve | serve | team | no | standard | |
| 929 | Service error | service-error | team | no | standard | |
| 936 | Let | let | team | no | standard | |
| 930 | Attack error | attack-error | team | no | standard | |
| 940 | Player error | player-error | team | yes | standard | |
| 935 | Net attack | net-attack | team | no | standard | |
| 934 | Net touch | net-touch | team | no | standard | |
| 933 | Repeat point | repeat-point | team | no | standard | |
| 946 | Challenge | challenge | team | no | standard | |
| 947 | Challenge correct | challenge-correct | team | no | standard | |
| 948 | Challenge incorrect | challenge-incorrect | team | no | standard | |
| 943 | Timeout | timeout | team | no | standard | |
| 942 | Medical timeout | timeout-medical | team | no | standard | |
| 937 | Yellow card | yellow-card | team | yes | standard | |
| 938 | Red card | red-card | team | yes | standard | |
| 939 | Black card | black-card | team | yes | standard | |
| 944 | Set point | set-point | team | no | standard | |
| 941 | Set won | set-won | team | yes | standard | |
| 945 | Match point | match-point | team | no | standard | |
| 932 | Point cancelled | cancel-point | team | yes | standard |
Statistics 20
Split into team statistics (in participants[].stats) and person statistics (in sub_participants[].stats). Match by code, not by position.
Team 10
| id | Name | Code | Data type |
|---|---|---|---|
| 105 | Service faults | service_faults | integer |
| 153 | Errors | errors | integer |
| 414 | Total points won | TP_won | integer |
| 8 | Yellow cards | yellow_cards | integer |
| 9 | Red cards | red_cards | integer |
| 415 | Black cards | black_cards | integer |
| 109 | Challenges | challenges | integer |
| 110 | Challenges correct | challenges_correct | integer |
| 416 | Challenges incorrect | challenges_incorrect | integer |
| 403 | Is server side | service | binary_text |
Person 10
| id | Name | Code | Data type |
|---|---|---|---|
| 105 | Service faults | service_faults | integer |
| 153 | Errors | errors | integer |
| 414 | Total points won | TP_won | integer |
| 8 | Yellow cards | yellow_cards | integer |
| 9 | Red cards | red_cards | integer |
| 415 | Black cards | black_cards | integer |
| 109 | Challenges | challenges | integer |
| 110 | Challenges correct | challenges_correct | integer |
| 416 | Challenges incorrect | challenges_incorrect | integer |
| 403 | Is server side | service | binary_text |