Research
Buckler API notes
SF6 Statsruns on undocumented web data routes behind Street Fighter 6 Buckler's Boot Camp. We documented what we observed and published it as a community reference. It is unofficial, not affiliated with Capcom, and focused on read-only data.
What's in the documentation
- Getting startedHow the routes work, what you need, and how to stay conservative.
- AuthenticationSession cookies, header expectations, and refresh behavior.
- Endpoint referenceObserved profile, battle log, search, and ranking routes.
- Observed schemasField-level notes with confidence labels per observation.
- Errors and versioningHTTP vs embedded status codes, stale build IDs, empty shells.
- Ethical useRate limits, access controls, and what not to do.
Read before you build
- It is not a REST API
- Buckler exposes Next.js page-data routes for its own frontend. Routes, fields, and auth behavior can change without notice. The docs carry confidence labels so you know what was reproduced and what was seen once.
- No credentials here
- The repository does not provide session bypasses, private game service auth, replay downloads, or archived user responses. You use your own session from your own logged-in browser, at your own rate.
- Handle change
- Validate both HTTP status and embedded status codes. Expect to rediscover the current Next.js build ID after a Capcom deploy. Treat every field as nullable.
- Contribute observations
- Issues and pull requests are welcome on GitHub if you observe new behavior through normal use of the public frontend. The repo has evidence and sanitization requirements in CONTRIBUTING.md.
Unofficial community project. Street Fighter and Buckler's Boot Camp are trademarks of Capcom.