Bet APIblaze.bet.br ↗
Get the 20 most recent Blaze Double roulette outcomes via API. Returns color, roll number, timestamp, and provably fair server seed for each round.
What is the Bet API?
The Blaze Double API returns the 20 most recent completed rounds from the Blaze Double roulette game through a single endpoint, get_latest_results. Each result includes 6 fields: a round ID, creation timestamp, color outcome, color code, roll number (0–14), and provably fair server seed. No input parameters are required to call the endpoint.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/e4a2be81-43cb-49f7-8a63-06cc1c8d28bf/get_latest_results' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace blaze-bet-br-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Blaze Double game results — fetch recent rounds."""
from parse_apis.blaze_bet_br_api import BlazeBet, ParseError
client = BlazeBet()
# Fetch the latest Double rounds; limit= caps total items yielded.
for result in client.results.list(limit=5):
print(result.color, result.roll, result.created_at)
# Drill into one result for its provably fair seed.
try:
latest = client.results.list(limit=1).first()
except ParseError as e:
print(f"Upstream issue: {e.code}")
latest = None
if latest is not None:
print(f"Round {latest.id}: color_code={latest.color_code}, seed={latest.server_seed}")
print("exercised: results.list")
Returns the 20 most recent completed Double game rounds in a single request. Each result includes the color outcome (white/red/black), the roll number (0-14), an ISO-8601 UTC timestamp, and the provably fair server seed. Results are ordered from newest to oldest; a new round completes roughly every 30 seconds. No input parameters. The game is only served to Brazilian visitors; when the request is refused for geographic reasons the call returns a blocked envelope and is retried from another location.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of results returned",
"results": "array of game round objects, each containing id, created_at, color, color_code, roll, and server_seed"
},
"sample": {
"data": {
"total": 20,
"results": [
{
"id": "4ekjyVyW19",
"roll": 10,
"color": "black",
"color_code": 2,
"created_at": "2026-09-11T20:05:16.630Z",
"server_seed": "REDACTED_SECRET"
},
{
"id": "2O1ByZyLrK",
"roll": 0,
"color": "white",
"color_code": 0,
"created_at": "2026-09-11T20:04:46.556Z",
"server_seed": "REDACTED_SECRET"
},
{
"id": "eRlvPKPW1j",
"roll": 7,
"color": "red",
"color_code": 1,
"created_at": "2026-09-11T20:01:46.069Z",
"server_seed": "REDACTED_SECRET"
}
]
},
"status": "success"
}
}About the Bet API
What the API Returns
The get_latest_results endpoint delivers the 20 most recently completed Blaze Double game rounds, ordered from newest to oldest. The response contains a total integer confirming the count, and a results array where each object carries a unique round id, a created_at timestamp, the winning color label (white, red, or black), a color_code numeric identifier, the roll value (an integer from 0 to 14), and a server_seed string used for provably fair verification.
Provably Fair Verification
The server_seed field in each result is the hash committed by the platform before the round resolves. Developers can use it alongside the other round fields to verify that outcomes were not manipulated after the fact, following standard provably fair protocols. This makes the API useful for building third-party audit tools or transparency dashboards.
Endpoint Behavior and Scope
The endpoint requires no query parameters — every call returns the same fixed window of the 20 latest rounds. There is no pagination, no filtering by color or roll range, and no historical lookup beyond the most recent 20 entries. created_at timestamps allow consumers to detect new rounds by comparing against their last-seen record.
The Bet API is a managed, monitored endpoint for blaze.bet.br — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when blaze.bet.br changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official blaze.bet.br API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a live Blaze Double result tracker displaying the last 20 outcomes with color-coded indicators
- Run a provably fair audit tool that recomputes round outcomes from the server_seed field
- Analyze color distribution (white/red/black) across recent rounds to spot short-term frequency patterns
- Alert users when a specific color sequence or roll number repeats across consecutive results
- Log round data into a time-series database using created_at timestamps to study outcome intervals
- Display a public fairness feed embedding server_seed values for on-demand verification
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.