one-vv3619 APIone-vv3619.com ↗
Access round history, live game status, and top-bet leaderboard for the 1win Double wheel game via 3 structured JSON endpoints.
What is the one-vv3619 API?
The one-vv3619.com API exposes 3 endpoints covering the 1win Double wheel game: round history, live game status, and a top-bets leaderboard. The get_round_history endpoint returns the 30 most recent completed rounds, each including the winning colour, payout multiplier, provably-fair data (SHA512 digest, salt, and check value), and UTC timestamp. This makes it straightforward to track outcomes, verify fairness data, or build statistical tooling around the red/black/green wheel.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/8bc59c69-8845-459a-bd3b-913bf249481f/get_round_history' \ -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 one-vv3619-com-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: 1win Double Game API — game status, round history, top bets."""
from parse_apis.one_vv3619_com_api import Double, Period, OrderBy, InputFormatInvalid
client = Double()
# Current game snapshot: players online, latest round, recent colour streaks.
status = client.game_status.get()
print(f"Players online: {status.players_online}")
print(f"Latest round: {status.latest_round.outcome} (x{status.latest_round.payout_multiplier})")
print(f"Recent colours — red: {status.recent_outcome_counts.red}, "
f"black: {status.recent_outcome_counts.black}, "
f"green: {status.recent_outcome_counts.green}")
# Recent completed rounds with provably-fair digests.
for rnd in client.rounds.list(limit=5):
print(f"{rnd.round_id[:8]} {rnd.outcome:>5} x{rnd.payout_multiplier} "
f"algo={rnd.provably_fair.algorithm}")
# Top weekly bets ordered by multiplier.
try:
for bet in client.bets.list(period=Period.WEEK, order_by=OrderBy.MULTIPLIER, limit=3):
print(f"Bet {bet.bet_id[:8]} ${bet.bet_amount_usd:.2f} → ${bet.win_amount_usd:.2f} "
f"x{bet.coefficient} {bet.currency} round={bet.round_outcome}")
except InputFormatInvalid as e:
print(f"Invalid input: {e.message}")
print("exercised: game_status.get / rounds.list / bets.list")
Returns the most recent completed rounds of the Double game, newest first, as the game client shows them. Each round carries its identifier, the winning colour (red, black or green), the fixed payout multiplier for that colour, the provably-fair data (SHA512 digest, salt and check string) and round_time_utc, which is derived from the time embedded in the round identifier (UUIDv7) rather than reported by the site. The site exposes a fixed window of the latest 30 rounds; there is no pagination or filtering. Takes no parameters and costs four upstream requests per call (a demo game session is minted on every invocation).
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer number of rounds returned (currently always 30)",
"rounds": "array of round records, newest first (round_id, outcome, payout_multiplier, round_time_utc, variant, provably_fair{algorithm,salt,check_string,digest})"
},
"sample": {
"data": {
"count": 30,
"rounds": [
{
"outcome": "red",
"variant": "default",
"round_id": "01a1211e-af39-747a-810d-68bf90864969",
"provably_fair": {
"salt": "cb8ab2aeec2d0d91a1ccf638a9f01c30",
"digest": "dedeaeb93eceb21d40809e301d750dc9a30439be399d7df7da7d1727e8ceb7b06b934d159574b9ef50a68d5a501e3dbda0c9388f6c0867f176f33d2dc780d356",
"algorithm": "SHA512",
"check_string": "01a1211e-af39-747a-810d-68bf90864969-red-cb8ab2aeec2d0d91a1ccf638a9f01c30"
},
"round_time_utc": "2026-10-09T14:43:41.497Z",
"payout_multiplier": 2
}
]
},
"status": "success"
}
}About the one-vv3619 API
Round History
get_round_history takes no inputs and returns an array of up to 30 completed round records ordered newest-first. Each record includes round_id, outcome (red, black, or green), payout_multiplier (2 for red and black, 14 for green), round_time_utc, variant, and a provably_fair object containing the algorithm (SHA512), salt, and check value. The top-level count field tells you how many rounds are in the payload — currently always 30.
Live Game Status
get_game_status returns a single-call snapshot of everything happening right now. Fields include players_online (integer count of currently connected players), latest_round (same shape as a history record), checked_at_utc (ISO-8601 snapshot timestamp), recent_outcomes (array of the last 30 colour strings, newest first), recent_outcome_counts (per-colour tallies for red, black, and green), recent_rounds_considered, and payout_multipliers (the fixed colour-to-multiplier mapping). This endpoint is suited to dashboards that need current state without polling multiple calls.
Top-Bets Leaderboard
get_top_bets mirrors the game's "Top" tab. It accepts two optional parameters: period (day, week, or month) and order_by (bet amount in USD or win multiplier). The response returns up to 30 bet records, each carrying bet_id, created_at, user_id, currency, bet_amount, bet_amount_usd, win_amount, win_amount_usd, and a usd_exch rate. The period and order_by fields echo back the applied filters so you can confirm what the response represents.
The one-vv3619 API is a managed, monitored endpoint for one-vv3619.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when one-vv3619.com 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 one-vv3619.com 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?+
- Track colour frequency distributions over the last 30 rounds using
recent_outcome_countsfromget_game_status. - Verify provably-fair round integrity by cross-checking SHA512 digests, salts, and check values from
get_round_history. - Build a live activity widget showing
players_onlineandlatest_roundoutcome fromget_game_status. - Compile weekly leaderboards of highest-USD bets using
get_top_betswithperiod=weekandorder_by=bet_amount. - Analyse green (x14) hit frequency relative to red and black over sliding 30-round windows from the
recent_outcomesarray. - Monitor
win_amount_usdandbet_amount_usdspread across currencies on the daily top-bets list to study stake distribution.
| 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.
Does 1win provide an official public developer API for the Double game?+
What does `get_game_status` return that `get_round_history` does not?+
get_game_status adds fields not present in get_round_history: players_online (live connected-player count), checked_at_utc (snapshot timestamp), recent_outcome_counts (per-colour tallies), payout_multipliers (the colour-to-multiplier mapping), and recent_outcomes as a flat colour array. get_round_history focuses solely on the ordered array of full round records.Can I retrieve more than 30 rounds of history?+
get_round_history endpoint currently returns exactly 30 rounds and does not accept pagination or offset parameters. You can fork this API on Parse and revise it to add a pagination parameter if deeper history is needed.Does the API cover other 1win casino games beyond Double?+
Are individual player profiles or account balances exposed through any endpoint?+
get_top_bets endpoint does include a user_id field alongside bet and win amounts, but full profile details are not exposed. You can fork the API on Parse and revise it if adjacent player-level fields become available.