Official player-data API for Arena match and draft history (covering all platforms, including mobile)
Summary
Community tools such as 17Lands track drafts, decks and results by reading the desktop client’s “Detailed Logs (Plugin Support)” file. That only works on desktop, so mobile players are left out. It’s also fragile on desktop, because trackers break when the log format changes. Please provide an official, opt-in API that lets players access their own draft and match history and authorize third-party tools to read it.
The problem today
Mobile players have no access at all. Tested on a Pixel 9 (Android 17) with Arena 2026.65: there’s no Detailed Logs option, and after a full Premier Draft and a match, the client’s session logs contained no draft picks, deck submissions or game results.
Desktop tracking relies on scraping the log. Trackers read a debug log that was never meant as a public interface, so client updates can break them.
The workaround is extreme: screen-recording entire drafts (several GB per hour) and extracting picks from the video afterward.
Proposed: Arena Player Data API
Player consent via OAuth: a player authorizes a tool through their Wizards account, can choose what it gets (for example draft history, match results and decklists, separately), and can revoke access anytime.
Data:
event entries and records
draft packs and picks
deck submissions
game and match results (win/loss, play/draw, mulligans, duration)
optionally, game-by-game detail later on
Delivery: a history endpoint plus webhooks or a polling feed for recent games, with rate limits Wizards controls.
Self-service export: the same data downloadable from a player’s account page, for players who don’t use third-party tools.
Why an API is a good long-term solution
Works the same everywhere: desktop, Android, iOS and any future platform, with no per-client work.
No cost to the device: no logging overhead, storage or battery use, which matters most on mobile.
Wizards controls privacy and scope: players opt in explicitly and can revoke, and Wizards decides exactly what’s shared. That’s better than tools reading raw debug logs.
Stable for developers: a versioned API replaces reverse-engineering logs, so fewer trackers break after client updates.
Community value: Limited datasets like 17Lands’ would include mobile players, giving everyone a more complete picture of the format.
Fallback if an API isn’t feasible soon: opt-in detailed logs on mobile
Off by default, same as desktop. Players who don’t enable it pay nothing.
A lighter “tracker” level: only event joins, draft packs and picks, deck submissions, and game and match results. On desktop, play-by-play game-state messages are about two-thirds of Player.log, which runs about 12 MB for a session with one draft and one match.
Compress while writing: the desktop log compresses about 13× (12 MB down to 0.9 MB).
Keep only the last few sessions, as the mobile client already does with its existing logs.
Store it where the player can reach it: the app’s data folder on Android (reachable over USB), and the app’s Documents folder via Finder or Files sharing on iOS.
Thanks for considering this. Mobile is a great way to draft, and it would be great if those games counted toward players’ own stats and the community’s data too.