Try every endpoint against live sample data
Realistic fixtures, live scores, odds and statistics across every sport we cover — no signup, no API key, no rate limit. See the exact JSON your integration will receive before you write a line of code.
This is what running requests actually feels like
A hands-off preview — it runs a few requests, then jumps back into history. The real thing is right below.
// waiting…
Loops automatically — scroll down to #live-console and drive it yourself.
Realistic Sample Data
Fixtures, scores, odds and statistics across every sport, matching production field-for-field.
Try Before You Build
See exact response shapes and error cases before you sign up or write a line of code.
Generated Code Snippets
Every sandbox call generates the matching cURL, JavaScript, Python and more.
Webhooks & WebSocket
Simulated live match events, so you can test real-time integrations before going live.
Your own mini API dashboard
Run requests, watch them stack up in your history, and see exactly what changed between calls — the same rhythm as a real integration, minus the API key.
// Click "Run Request" to see a response here.
Rate limited!
You just burned through 150 sandbox calls in one sitting — respect. This is exactly what your users will hit on the Free tier too. Reset the demo counter to keep exploring, or see what more headroom looks like.
What the Orbistats sandbox actually does
A sandbox environment is a copy of the real API that returns realistic sample data instead of live results. It exists so you can build against the exact shape of every response — field names, nesting, error codes, pagination — before an account, a key or a monthly quota enters the picture. Every sandbox response mirrors its production counterpart exactly, so the request you write today against sandbox.orbistats.com keeps working unchanged once you point it at api.orbistats.com with a real key.
Upcoming fixtures for a sport, filterable by league, team or date range. Run it in the sandbox to see the exact list, pagination and field shape before you filter by your own league or team.
| Parameter | Type | Required | Description |
|---|---|---|---|
| league | string | No | Competition slug, e.g. premier-league. |
| team | string | No | Team slug or ID to filter fixtures for one club. |
| date_from / date_to | date | No | ISO 8601 date range. Defaults to the next 14 days. |
Every match currently in play, with score, clock, period and the most recent event. The sandbox rotates through simulated live matches so the clock and score actually move between calls.
Completed fixtures with the final score, so you don't have to reconstruct results by polling the live-scores endpoint until a match ends.
| Parameter | Type | Required | Description |
|---|---|---|---|
| league | string | No | Competition slug. |
| date_from / date_to | date | No | ISO 8601 date range. |
The current league table — played, won, drawn, lost, goal difference and points — updated automatically as results are confirmed.
| Parameter | Type | Required | Description |
|---|---|---|---|
| league | string | Yes | Competition slug. |
| season | string | No | Defaults to the current season. |
Season-level team statistics — shots, possession, cards and sport-specific metrics. A matching /statistics/player/{player_id} endpoint returns individual player numbers for the same season.
Pre-match and live odds normalized into a single format across sportsbooks. Sandbox odds move on every call so you can test how your pricing logic reacts to a changing number.
Team and player directories with the stable IDs used throughout the rest of the API — the IDs a sandbox response returns here are the same ones you'll pass to statistics, lineups and events.
Season-by-season historical match data for backtesting models and head-to-head pages. Sandbox history covers a sample range so you can validate pagination and cursor logic before pulling a full archive.
The sandbox includes a test receiver that fires signed webhook payloads on a short interval, plus a WebSocket endpoint that streams simulated live match events — build and verify your real-time handling before there's real traffic to test against.
The sandbox covers every sport we support
Swap the {sport} path segment on any endpoint above — the sandbox returns realistic sample data for each one using the same resource shape.
Common sandbox issues
The handful of things that trip people up when moving from sandbox to production.
My sandbox data doesn't match real fixtures
That's expected — sandbox data is realistic but not live. Team names, IDs and dates are sample values; only the response shape is guaranteed to match production exactly.
Requests fail once I switch to production
The open sandbox at sandbox.orbistats.com needs no key, but api.orbistats.com always does. Add Authorization: Bearer YOUR_API_KEY when you move off the sandbox host.
Live scores or odds look static
Sandbox live data rotates on a short interval to simulate an in-progress match. If two calls look identical, wait a few seconds and call again.
Common questions
What people ask before their first sandbox call.
Do I need an API key to use the Orbistats sandbox?
No. The sandbox is open at https://sandbox.orbistats.com/ with no signup and no API key. It's the fastest way to see real response shapes before you create an account.
Is sandbox data real or made up?
Sandbox responses are realistic sample data, not live results. Every field, status and error case mirrors production exactly, so code you write against the sandbox works unchanged once you switch to a real API key.
Does the sandbox have a rate limit?
No. Sandbox calls never count against a quota or rate limit, so you can explore every endpoint and parameter freely while you build.
Can I use the sandbox to test webhooks and the WebSocket stream?
Yes. The sandbox includes a webhook test receiver and a WebSocket endpoint that emits simulated live match events, so you can build and test real-time integrations before going live.
What's the difference between the sandbox and a sandbox API key?
The open sandbox at sandbox.orbistats.com needs no account at all. Once you sign up, your account also gets a personal sandbox key that behaves the same way but is tied to your dashboard, useful for team demos and CI pipelines.
Related pages
Explore more of the developer platform.
API Reference
Every endpoint, sport by sport.
Quickstart
Make your first request in five minutes.
SDKs
Official client libraries and code examples.
Documentation
The full developer documentation hub.
Status
Live uptime and incident history.
Changelog
What's new across the API.
Start free. Upgrade when you need enterprise SLAs.
Self-serve API keys for developers today — dedicated infrastructure, custom feeds and SLAs when you're ready.