1xlite 36553 API1xlite-36553.pro ↗
Get live basketball scores, period scores, game clock, and finished status from the 1xlite live feed. Two endpoints: list all games or fetch one by ID.
What is the 1xlite 36553 API?
This API exposes 2 endpoints that pull live basketball game data from the 1xlite live feed, returning up to 250 in-progress or recently finished games per call. list_live_basketball_games returns the full feed in one round trip — teams, current totals, per-period scores, game clock in seconds, and a finished flag. get_live_basketball_game returns the same shape for a single game looked up by its numeric game_id.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/10a787d4-19c8-4f5d-9a39-71fc12e23650/list_live_basketball_games' \ -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 1xlite-36553-pro-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: 1xLite Live Basketball Feed — browse live games, drill into one."""
from parse_apis.api_1xlite_36553_pro_api import Basketball, GameNotFound
client = Basketball()
# List all live basketball games, capped at 5 items.
for game in client.games.list(limit=5):
score_display = game.full_score or "not started"
print(f"{game.home_team} vs {game.away_team} ({game.league}) — {score_display}")
# Drill into the first live game for full detail including period scores.
first_game = client.games.list(limit=1).first()
if first_game is not None:
detail = client.games.get(game_id=str(first_game.game_id))
print(f"\n{detail.home_team} vs {detail.away_team}")
print(f" Score: {detail.score.home} - {detail.score.away}")
print(f" Final: {detail.is_final}")
if detail.period_scores:
for ps in detail.period_scores:
print(f" {ps.name}: {ps.home}-{ps.away}")
# Show a typed error catch for a lookup that can fail.
try:
client.games.get(game_id="0")
except GameNotFound as e:
print(f"\nExpected not-found error: {e.message}")
print("\nexercised: games.list / games.get / GameNotFound")
Returns every basketball game currently present in the site's live feed (in-progress games, games about to start, and games that finished within the last few minutes), one row per game, in the site's own order. A single round trip; no pagination (the live feed for one sport is small, typically a few dozen games). Scores are null before tip-off; timer_seconds is the site's game clock and timer_counts_down says whether it counts down to the end of the period (true) or up from the start of the game (false). is_final is true when the site marks the game as finished; a finished game keeps its full_score and period_scores until the site removes it from the live feed. Team and period names are in English.
No input parameters required.
{
"type": "object",
"fields": {
"count": "number of games returned",
"games": "array of live game objects (see sample); game_id is the identifier accepted by get_live_basketball_game",
"games[].score": "object {home, away} with the current total score (null before tip-off)",
"games[].is_final": "boolean: true when the site marks the game finished (full_score is then the final score)",
"games[].full_score": "current total score formatted as 'home:away', or null before tip-off",
"games[].period_format": "period format string from the site such as 4x10, or null",
"games[].period_scores": "array of {period, name, home, away} per period played so far; home/away are null for a period not yet scored",
"games[].timer_seconds": "game clock in seconds, or null when the site publishes no clock",
"games[].start_timestamp": "scheduled tip-off as a Unix timestamp (seconds)",
"games[].timer_counts_down": "boolean: true when timer_seconds counts down within the period, false when it counts up"
},
"sample": {
"data": {
"count": 2,
"games": [
{
"score": {
"away": 79,
"home": 92
},
"league": "WNBA",
"country": "United States",
"game_id": 754681394,
"is_final": false,
"away_team": "Connecticut Sun (Women)",
"home_team": "Minnesota Lynx (Women)",
"full_score": "92:79",
"status_text": "3 min remaining",
"period_format": "4x10",
"period_scores": [
{
"away": 12,
"home": 27,
"name": "1st quarter",
"period": 1
},
{
"away": 31,
"home": 28,
"name": "2nd quarter",
"period": 2
},
{
"away": 24,
"home": 21,
"name": "3rd quarter",
"period": 3
},
{
"away": 12,
"home": 16,
"name": "4th quarter",
"period": 4
}
],
"timer_seconds": 176,
"current_period": 4,
"start_timestamp": 1789922700,
"timer_counts_down": true,
"current_period_name": "4th quarter"
},
{
"score": {
"away": 87,
"home": 101
},
"league": "Spain Super Cup",
"country": "Spain",
"game_id": 754681565,
"is_final": true,
"away_team": "Barcelona",
"home_team": "FIATC Joventut Badalona",
"full_score": "101:87",
"status_text": null,
"period_format": "4x10",
"period_scores": [
{
"away": 23,
"home": 32,
"name": "1st quarter",
"period": 1
},
{
"away": 23,
"home": 20,
"name": "2nd quarter",
"period": 2
},
{
"away": 22,
"home": 19,
"name": "3rd quarter",
"period": 3
},
{
"away": 19,
"home": 30,
"name": "4th quarter",
"period": 4
}
],
"timer_seconds": 2400,
"current_period": null,
"start_timestamp": 1789923600,
"timer_counts_down": false,
"current_period_name": "Game finished"
}
]
},
"status": "success"
}
}About the 1xlite 36553 API
What the API Returns
Both endpoints return the same core data shape. Each game object includes full_score (formatted as home:away), a score object with separate home and away integers, a is_final boolean that flips to true when the feed marks the game finished, and period_scores — an array of {period, name, home, away} entries for every period played so far. Periods not yet scored carry null for home and away.
Game Clock and Period Format
The timer_seconds field gives the game clock as an integer number of seconds, or null when the feed does not publish a clock for that game. timer_counts_down tells you whether that clock counts down within the period (true) or up (false). The period_format string (e.g. 4x10) describes the period structure used by the site for that game. start_timestamp is the scheduled tip-off as a Unix timestamp in seconds.
Endpoints and Parameters
list_live_basketball_games takes no inputs and returns the full live feed as a flat array under games, plus a top-level count. The game_id from any row is the only required parameter for get_live_basketball_game. Passing a game_id that is no longer present in the live feed will not return a result — IDs are only valid while the game is active or recently finished.
Coverage Scope
The feed covers basketball only. It reflects whichever games the 1xlite live feed includes at the time of the call — typically a mix of professional leagues from multiple countries. There is no historical data; all responses are point-in-time snapshots of the current live state.
The 1xlite 36553 API is a managed, monitored endpoint for 1xlite-36553.pro — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 1xlite-36553.pro 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 1xlite-36553.pro 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?+
- Display live basketball scoreboards using
full_scoreandperiod_scoreswithout polling multiple sources. - Trigger alerts when
is_finalflips totruefor a trackedgame_id. - Build a period-by-period scoring breakdown using the
period_scoresarray andperiod_formatstring. - Drive a live game clock widget using
timer_secondsandtimer_counts_downtogether. - Filter in-progress games from recently finished ones using the
is_finalflag on the list endpoint. - Map scheduled tip-off times to local timezones using
start_timestampfor pre-game display.
| 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 1xlite have an official public developer API?+
What does `list_live_basketball_games` return versus `get_live_basketball_game`?+
list_live_basketball_games returns all basketball games currently in the live feed as an array under games, with a top-level count. get_live_basketball_game takes a single game_id string and returns one game object in the same shape — useful when you already know which game you want and don't need the full list.Is `timer_seconds` always populated?+
timer_seconds is null when the feed does not publish a clock for a given game. Not every game in the feed includes clock data — you should treat null as a valid state rather than an error. timer_counts_down is still present but its value is only meaningful when timer_seconds is non-null.