Custom Match History & Developer API Ecosystem
## Background & Value Proposition
The Dead by Daylight competitive, tournament, and community-driven content ecosystems rely heavily on Custom Matches. Currently, capturing and analyzing match data requires manual recording or third-party screen-scraping software. Providing an official, privacy-first API framework would allow community developers to build robust analytical tools, tournament tracking systems, and stat dashboards safely.
### 1. Ephemeral Custom Match Retention
- **Mechanism:** Implement short-term backend retention for all completed Custom Matches.
- **Parameters:** Data are stored privately for a 3 days before permanent deletion.
- **Impact:** Minimizes server storage overhead for Behaviour while providing an adequate window for data extraction.
### 2. Secure OAuth 2.0 Authorization System
- **Mechanism:** Create an authentication system mirroring user-permission like Twitch or Discord.
- **User Control:** Players must explicitly grant read-only permissions to verified third-party developer applications via a Behaviour Account login prompt.
- **Security:** Users retain the ability to view authorized applications and instantly revoke match history access at any time through their account settings.
### 3. Developer Web API
- **Endpoint:** Introduce a secure endpoint (e.g., /matches/custom/history).
- **Data Payload:** Returns JSON data essential match telemetry including map ID, character choices, selected perks, add-ons, items, and basic end-game scoring events. (similar to existing match history at `stats.deadbydaylight.com/match-history/`)
- **Privacy Guardrails:** The API strictly filters out public data, returning results only if the querying player has actively authenticated the request.
Comments