1wlucb API1wlucb.life ↗
Retrieve the 20 most recent Lucky Jet crash game rounds from 1win, including multiplier coefficients and provably fair hash/salt data for each outcome.
What is the 1wlucb API?
The Lucky Jet 1win API exposes 1 endpoint — get_round_history — that returns the 20 most recent completed rounds from the Lucky Jet crash game. Each response includes the round ID, crash multiplier coefficient, and provably fair hash and salt fields, giving developers direct access to recent game history and the data needed to verify outcome integrity independently.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/2b7d091d-f8a1-483b-b734-63b3d8a81e53/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 1wlucb-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 round history — fetch recent crash rounds with provably fair data."""
from parse_apis.api_1wlucb_life_api import LuckyJet, ParseError
client = LuckyJet()
# Retrieve the most recent rounds, capped at 10 items
try:
for round in client.rounds.list(limit=10):
print(f"Round {round.id}: {round.coefficient}x")
except ParseError as e:
# Game server may rotate sessions; surface the structured error code
print(f"Parse failure [{e.code}]: {e}")
# Grab the first round for detailed provably-fair verification info
top_round = client.rounds.list(limit=1).first()
if top_round is not None:
print(f"Verifying round {top_round.id}")
print(f" Coefficient: {top_round.coefficient}x")
print(f" Hash: {top_round.hash}")
print(f" Salt: {top_round.salt}")
print("exercised: rounds.list")
Returns the 20 most recent completed Lucky Jet rounds. Each round includes its crash multiplier coefficient and provably fair hash/salt for verification. The endpoint establishes a demo game session internally to access the game server; no authentication is required from the caller.
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer, number of rounds returned",
"rounds": "array of round objects, each containing id, coefficient, hash, and salt"
},
"sample": {
"data": {
"count": 20,
"rounds": [
{
"id": "2d8efb5e-494d-4e5e-b188-e1acd83dd1fc",
"hash": "REDACTED_SECRET",
"salt": "REDACTED_SECRET",
"coefficient": 9.59
},
{
"id": "e15db390-dce4-4c1f-b264-f9bcc6def199",
"hash": "REDACTED_SECRET",
"salt": "REDACTED_SECRET",
"coefficient": 1.53
}
]
},
"status": "success"
}
}About the 1wlucb API
What the API Returns
The get_round_history endpoint returns a JSON object with a count integer confirming how many rounds are included and a rounds array. Each element in the array contains four fields: id (unique round identifier), coefficient (the crash multiplier at which that round ended), hash (the provably fair hash string), and salt (the salt value used in the fairness proof). No input parameters are required — calling the endpoint returns the latest 20 completed rounds immediately.
Provably Fair Verification
The hash and salt fields returned per round are the inputs needed to independently verify that each outcome was not manipulated after the fact. Developers building audit tools or statistical trackers can use these values to confirm that the coefficient for a given round is consistent with its declared hash and salt, following Lucky Jet's standard provably fair scheme.
Coverage and Freshness
The endpoint always reflects the 20 most recently completed rounds at the time of the request. There is no pagination and no filtering by date range or coefficient threshold. Because Lucky Jet rounds complete quickly, repeated polling can be used to build a local time-series of results. The data covers the Lucky Jet game variant hosted on the 1win platform specifically.
The 1wlucb API is a managed, monitored endpoint for 1wlucb.life — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 1wlucb.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 1wlucb.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?+
- Build a coefficient history chart showing the last 20 Lucky Jet outcomes in real time
- Automate provably fair audits by collecting
hashandsaltvalues and verifying them against published coefficients - Detect statistical streaks or dry spells in crash multipliers by polling
get_round_historyat regular intervals - Store a rolling dataset of
coefficientvalues for distribution analysis across sessions - Cross-reference round
idvalues with user bet records to reconcile game outcomes - Monitor average multiplier trends over time using repeated calls to the single endpoint
| 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 developer API for Lucky Jet game data?+
What exactly does `get_round_history` return for each round?+
rounds array contains four fields: id (the round identifier), coefficient (the crash multiplier), hash (the provably fair hash), and salt (the salt for fairness verification). The top-level count field confirms the number of rounds returned, which is always 20.