1wubgh API1wubgh.life ↗
Access Lucky Jet crash game data from 1win: last 20 completed rounds with provably-fair hashes, and live round state including multiplier, bets, and phase timing.
What is the 1wubgh API?
This API exposes two endpoints covering the Lucky Jet crash game on 1win: get_round_history returns the 20 most recently completed rounds with crash multipliers and provably-fair hashes, while get_current_round delivers a live snapshot of the round in progress — including its phase, live multiplier, bet counts, player bets, and scheduled phase-change timestamps. All data reflects what the game surface publicly displays with no authentication required.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/14fe3ad8-26a2-4c3a-8e49-3d1d81ced99e/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 1wubgh-life-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: Lucky Jet API — recent rounds and live round snapshot."""
from parse_apis.api_1wubgh_life_api import LuckyJet, ParseError
client = LuckyJet()
# Fetch the last 20 completed rounds and print crash multipliers.
for round in client.rounds.list(limit=5):
print(f"Round {round.round_id}: {round.multiplier}x (hash={round.hash[:16]}…)")
# Snapshot the current live round.
try:
current = client.current_rounds.get()
except ParseError as e:
print(f"Could not fetch live round: {e.code}")
raise
print(f"\nLive round {current.round_id} — phase: {current.state}, bets: {current.bet_count}")
print(f" RTP: {current.rtp} server_time: {current.server_time}")
print(f" bet range: {current.bet_limits.min}–{current.bet_limits.max} USD")
print(f" auto-cashout: {current.auto_cashout_limits.min}x–{current.auto_cashout_limits.max}x")
# Show provably-fair hash (salt is null until the round ends).
print(f" hash: {current.provably_fair.hash[:24]}… algo: {current.provably_fair.algorithm}")
# List visible player bets on the live round.
if current.top_bets:
for bet in current.top_bets[:3]:
status = f"cashed out at {bet.cashout_multiplier}x" if bet.cashout_multiplier else "in play"
print(f" {bet.user_name}: {bet.bet_size} {bet.currency} — {status}")
print("\nexercised: rounds.list / current_rounds.get")
Returns the most recent completed Lucky Jet rounds as the game itself shows them: the site exposes exactly the last 20 rounds, newest first, and offers no paging beyond that, so the response is always one fixed page. Each round carries its identifier, the crash multiplier (1 means the jet crashed immediately) and the provably-fair hash and salt that let a caller verify the outcome. No inputs; three upstream round trips (demo game launch, game authentication, history) per call.
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer, number of rounds returned",
"rounds": "array of the last 20 completed rounds, newest first; each has round_id (UUID), multiplier (number, crash multiplier), final_values (array of numbers, the per-slot final multipliers, currently a single value equal to multiplier), outcome (integer flag from the game, 0 in all observed rounds), hash and salt (hex strings for provably-fair verification)"
},
"sample": {
"data": {
"count": 20,
"rounds": [
{
"hash": "027ade6d6d162146157651ca0192efa8fcf13325eeed851b4ddd787cb7a88c91d09ba104bfccc255438d78489b54d72ed4ad3770835e702e481991b7ffa8d3eb",
"salt": "3f9f9725b98bce31b8d72088027899bc",
"outcome": 0,
"round_id": "cc7fa697-20e5-4999-b749-02a4233c882a",
"multiplier": 3.06,
"final_values": [
3.06
]
},
{
"hash": "fdc1f9a7a88c16072e9a50a1f4a2b6bfb1afeb75746d8a8f881e9207b3a42b0ed460f9f113fe2083df79711841608c4c3f6a4a5ca8f7ba27616c68fb401d3c88",
"salt": "68113a039ac07937bf606868a05ccffa",
"outcome": 0,
"round_id": "ea65c61d-519b-4a4e-8764-57695d6192c2",
"multiplier": 3.54,
"final_values": [
3.54
]
}
]
},
"status": "success"
}
}About the 1wubgh API
Round History
get_round_history returns a fixed array of the last 20 completed Lucky Jet rounds, newest first. Each entry includes a round_id (UUID), the crash multiplier, and provably-fair verification data. The source exposes exactly 20 rounds and provides no pagination cursor or offset parameter — every call returns the same fixed window of recent history. Use this endpoint to track recent crash outcomes, verify fairness hashes, or build a local time-series by polling at intervals.
Live Round State
get_current_round returns a snapshot of the active round. The state field reflects the current phase (betting, flying, or a transitional crashed state). state_changed_at and next_state_at are ISO-8601 UTC timestamps that tell you when the current phase began and when the next transition is expected — next_state_at is null during the flying phase since the crash point is not predetermined client-side. The live multiplier is included while the round is airborne.
Bets and Limits
The top_bets array lists the publicly visible player bets in the current round. Each entry carries user_id, user_name (nullable), currency, bet_size, and bet_size_usd. The bet_count integer gives the total number of bets placed regardless of how many appear in top_bets. Bet constraints are available via the bet_limits object, which includes min, max, max_win, default_bet, and a quick_bets array — all denominated in USD.
Provably Fair Data
Both endpoints surface provably-fair fields. get_current_round includes a provably_fair object with the algorithm, a pre-published hash for the round in progress, and a salt field that remains null until the round concludes and is revealed. The rtp field (e.g. 0.97) is also present on the current-round response, reflecting the game's stated return-to-player ratio.
The 1wubgh API is a managed, monitored endpoint for 1wubgh.life — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 1wubgh.life 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 1wubgh.life 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?+
- Logging Lucky Jet crash multiplier history by polling
get_round_historyand storing each newround_idandmultiplier. - Verifying provably-fair round outcomes by comparing the pre-published
hashfromget_current_roundagainst the revealedsaltafter round completion. - Building a round-phase monitor that tracks
state,state_changed_at, andnext_state_atto alert on betting windows. - Analyzing bet size distribution using
bet_size_usdvalues fromtop_betsacross successive rounds. - Displaying live player activity in a dashboard using
bet_countand thetop_betsarray fromget_current_round. - Checking game configuration such as
bet_limits.min,bet_limits.max, andquick_betsto inform a betting interface.
| 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 Lucky Jet data?+
How far back does the round history go?+
get_round_history always returns one fixed window of 20 rounds, newest first. You can build a longer local history by polling the endpoint at intervals and persisting new round_id entries.What does `next_state_at` return during the flying phase?+
flying phase, next_state_at is null because the crash point is not announced in advance. It becomes a populated ISO-8601 UTC timestamp during the betting phase, indicating when betting closes and the round begins.Does the API return historical round data beyond the last 20 rounds, or support filtering by multiplier range?+
get_round_history and the live state from get_current_round. There is no filtering by multiplier, date range, or round ID. You can fork this API on Parse and revise it to add a persistence layer or filtering endpoint using data you accumulate by polling.Are all player bets in a round returned, or only a subset?+
top_bets reflects only the bets the game surface publicly displays, which is a subset of total activity. The bet_count integer gives the full count of bets placed in the round. Individual bet details for non-displayed players are not currently exposed. You can fork this API on Parse and revise it to add additional bet data if a broader source becomes available.