Build on verified competitive data
Integrations
Stable schemas for verified outcomes and event-driven updates. Connect your backend to StatForge and ship consistent outcomes across your product.
- Integrate once.
- Use one contract.
- Expose outcomes your system can trust.
What you can build
StatForge powers systems where results must be correct, consistent, and defensible:
- Leaderboards and standings backed by verified match records
- Player profiles and match history that match your admin view
- Bots, companion apps, and partner integrations on the same data surface
Every surface reads from the same verified source, with no drift between systems.
How integration works
StatForge is designed for backend-first integration.
Create an application
Define your project and environment (sandbox or production).
Issue scoped API keys
Keys are limited by capability and environment.
Call read endpoints from your backend
Never expose keys directly to clients.
Render responses in your product
API responses match public reference formats.
(Optional) Submit structured input for review
Available on plans that include submission scopes.
You are not assembling data from multiple systems. You are consuming a single, verified contract.
Scopes and access
Access is controlled through scoped API keys.
Typical read scopes:
- read:players
- read:matches
- read:leaderboards
Your key defines exactly what your application can access.
Higher plans expand:
- Request volume and rate limits
- Environment access
- Optional submission scopes for reports and evidence
Submission does not change outcomes directly. StatForge remains the source of final verification.
Example verified match
Illustrative record. Your API returns the same fields for your data.
- Match ID
- sf_match_12845
- Status
- VERIFIED
- Teams
- Northwind vs Aurora
- Winner
- Northwind
- Evidence
- Available
- Reviewed at
- 2026-04-12T21:14:00Z
Why this model works
Most integrations fail because data is inconsistent across systems.
StatForge removes that problem:
- One match ID across all surfaces
- One verified outcome per match
- One lifecycle your system can rely on
Your frontend, admin tools, and integrations stay aligned by default.
Start integrating
Auth patterns, first requests, and setup checklist.
Endpoints, concepts, and limits.
New to StatForge?
Create an application and generate sandbox keys.
Compare access, limits, and capabilities.
Public reference surfaces using the same API responses.
This page covers integration. For lifecycle, verification, and system behavior, see the Product page.