Dear Blizzard Developer Support Team,
My name is Yun jihwan, and I am developing KILL BET, a web service for managing and analyzing Overwatch matches, as part of the GOTO team.
KILL BET helps communities manage participants, team compositions, and match records for community-organized custom matches. It also helps players review their own performance after a match using supporting evidence.
We are currently designing analysis features for custom matches. We are also considering a future feature that would allow users to import and analyze their own Quick Play and Competitive match records without entering them manually. We would therefore appreciate guidance on officially available data, access procedures, and usage conditions.
- Supported Match Types and Available Data
For Custom Games, Quick Play, and Competitive Play, is there an official API or data export feature that provides any of the following?
- Match identifiers, game mode, map, match date and time, and outcome.
- Round start and end times, and match duration.
- Identifiers that distinguish participants and teams.
- Per-participant time played on each hero and timestamps of hero changes.
- Timestamps and associated participants for eliminations, deaths, and assists.
- Timestamps of respawns, resurrections, and ultimate ability use.
- Match summary statistics, such as damage and healing, by participant and hero.
- Objective progression records, such as point captures and payload movement.
In particular, we would like to know whether individual match records and chronological event data are available separately from cumulative career profile statistics. If only some of these data points are supported, we would appreciate clarification on the available subset.
- Intended Use of the Data
We intend to use the data to provide the following post-match information:
- Estimated teamfight segments based on the sequence of elimination and death events.
- Involvement in the first elimination of a teamfight, and how the match develops after early deaths.
- Events associated with recovery from a player-number disadvantage.
- Metric-by-metric comparisons of participants playing the same role in the same match.
- Statistical comparisons that account for hero changes and time played.
Each result would display the relevant events and timestamps so users can review the evidence behind the analysis. We plan to validate teamfight segmentation and evaluation criteria against actual matches, and withhold conclusions when records are insufficient or interpretation is uncertain.
- User Authentication and Access to Participant Information
For Quick Play and Competitive Play, our preferred approach is for users to connect their own Battle.net accounts and consent to data access.
Could you please clarify:
- Whether Battle.net authentication and user consent can enable access to a user’s own match history and statistics.
- What data from a match can be accessed with the consent of one participant.
- Whether separate consent is required from each participant to analyze other participants’ records.
- What restrictions apply to private profiles and identifiers belonging to other participants.
- Whether an identifier suitable for linking accounts within our service can be provided instead of a real name or email address.
We intend to process other participants’ data only within the officially permitted scope and incorporate the required consent and access restrictions into the service design.
- Official Access Procedures and Alternative Collection Methods
If relevant APIs or data services are available, please advise on developer registration, access applications, authentication methods, rate limits, and any test environment.
If these capabilities are not available through public APIs but may be accessible through a developer program, partnership, or limited pilot, we would appreciate information on the application process and required materials.
For custom matches, we are also considering having the match host manually upload logs generated by a Workshop script designed to record match events. Please let us know whether any official guidance or usage conditions apply to analyzing, storing, and displaying these logs in an external web service.
- Service Operation and Data Usage Conditions
We would like to clarify applicable requirements concerning data retention, deletion at a user’s request, sharing analysis results, and any licensing conditions that depend on whether the service is operated commercially.
KILL BET’s analysis features are currently in the design and initial validation stage, and we do not yet have a public service URL. If needed, we can prepare and provide feature specifications, data processing diagrams, and UI mockups.
If another team is responsible for this inquiry, could you please direct us to the appropriate contact channel or application process? If this falls outside the scope of this forum, we would appreciate guidance on the official channel for Overwatch data access and usage inquiries.
Thank you for your time and guidance.
Best regards,
Yun jihwan
GOTO | KILL BET Developer