Asian Bet Soccer APIasianbetsoccer.com ↗
Access live soccer scores, Asian handicap odds, upcoming match schedules, and bookmaker listings from asianbetsoccer.com via 5 structured API endpoints.
What is the Asian Bet Soccer API?
The Asian Bet Soccer API provides 5 endpoints covering live match scores, upcoming fixtures, odds monitoring, and reference data for leagues and bookmakers. The get_livescore endpoint returns real-time match state including score, match time, Asian handicap lines, and European odds from eight supported bookmakers. The monitor_odds_alerts endpoint lets you define filtering criteria — handicap line, league substring, and odds threshold — and returns only the matches that qualify.
curl -X GET 'https://api.parse.bot/scraper/722cb732-6512-4ace-9466-bb35e4ae5227/get_livescore?bookmaker=188Bet' \ -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 asianbetsoccer-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: AsianBetSoccer SDK — live scores, upcoming matches, and odds alerts."""
from parse_apis.asianbetsoccer_api import (
AsianBetSoccer, Bookmaker, BookmakerNotFound
)
client = AsianBetSoccer()
# Fetch live matches with Bet365 odds, capped to 5 results.
for match in client.matches.live(bookmaker=Bookmaker.BET365, limit=5):
print(match.home_team, "vs", match.away_team, "-", match.match_time, match.odds.euro1_cu)
# Upcoming matches for tomorrow — take the first one and inspect its odds.
upcoming = client.upcomingmatches.list(day_offset=1, limit=1).first()
if upcoming:
print(upcoming.home_team, "vs", upcoming.away_team, "at", upcoming.match_time)
print("Handicap:", upcoming.odds.h_line_cu, "Home:", upcoming.odds.h_odds_cu, "Away:", upcoming.odds.a_odds_cu)
# List all currently active leagues.
for league in client.leagues.list(limit=10):
print(league.id, league.name)
# Get bookmaker info (static list of supported providers).
info = client.bookmakerinfos.get()
print("Supported bookmakers:", list(info.bookmakers.keys()))
# Scan live matches for alerts matching criteria.
try:
result = client.alertresults.scan(championship="Czech", handicap="-0.5", odds_threshold=5.0)
print("Checked at:", result.checked_at)
print("Criteria:", result.criteria.championship, result.criteria.odds_threshold)
for alert in result.alerts_found:
print(alert.match, alert.euro1, alert.handicap)
except BookmakerNotFound as exc:
print(f"Invalid bookmaker: {exc.bookmaker}")
print("Exercised: matches.live / upcomingmatches.list / leagues.list / bookmakerinfos.get / alertresults.scan")
Fetch live scores and odds for currently playing and recently finished matches. Returns match details including teams, scores, match time, and full Asian handicap and European odds from the selected bookmaker. Data refreshes every 60 seconds on the source site.
| Param | Type | Description |
|---|---|---|
| bookmaker | string | Bookmaker name for odds data. |
{
"type": "object",
"fields": {
"matches": "array of match objects with id, league, home_team, away_team, score_home, score_away, match_time, odds, and status"
},
"sample": {
"data": {
"matches": [
{
"id": "1",
"odds": {
"tot": "1740",
"euro1_cu": "1.90",
"euro1_op": "1.82",
"euro2_cu": "3.30",
"euro2_op": "3.80",
"euroX_cu": "3.10",
"euroX_op": "3.25",
"a_odds_cu": "1.80",
"a_odds_op": "1.88",
"h_line_cu": "-0.5",
"h_line_op": "-0.5",
"h_odds_cu": "1.90",
"h_odds_op": "1.82",
"payout_cu": "-0.1%",
"payout_op": "0.5%",
"ou_line_cu": "2.25",
"ou_line_op": "2.25",
"over_odds_cu": "1.85",
"over_odds_op": "1.97",
"under_odds_cu": "1.85",
"under_odds_op": "1.73"
},
"league": "Vietnamese National Cup",
"status": "live",
"away_team": "Cong An TP Ho Chi Minh",
"home_team": "Nam Dinh FC",
"match_time": "4'",
"score_away": "0",
"score_home": "0"
}
]
},
"status": "success"
}
}About the Asian Bet Soccer API
Live Scores and Odds
The get_livescore endpoint returns an array of match objects for currently playing and recently finished matches. Each object includes id, league, home_team, away_team, score_home, score_away, match_time, status, and a full odds block. You select the bookmaker by passing one of eight accepted values to the bookmaker parameter: 188Bet, Bet365, Sbobet, Crown, 12Bet, 18Bet, AvgOdds, or Bet365 Live. Omitting the parameter falls back to a default. AvgOdds returns a market average rather than a single book's line.
Upcoming Fixtures
The get_next_games endpoint accepts a day_offset integer (0 for today, 1 for tomorrow, and so on) alongside the same bookmaker selector. Response objects mirror the live schema but without score fields, and match_time is expressed in UTC. This makes it straightforward to build a pre-match odds tracker or automate daily fixture ingestion.
Odds Alerting
monitor_odds_alerts scans all currently live matches and filters them against three optional criteria: handicap (e.g. -1.25, 0, 1.5), championship (case-insensitive partial match on league name), and odds_threshold (a numeric ceiling on euro1_cu). The response returns a criteria echo object, a checked_at ISO 8601 UTC timestamp, and an alerts_found array whose objects each carry match, league, euro1, handicap, time, and score fields.
Reference Endpoints
get_available_leagues returns leagues that have active or recently finished matches as an array of {id, name} objects — useful for populating dropdowns or validating championship filter strings before calling monitor_odds_alerts. get_available_bookmakers returns a single object mapping each bookmaker display name to its internal hash identifier, which reflects exactly the set of values accepted by the bookmaker parameter across the other endpoints.
The Asian Bet Soccer API is a managed, monitored endpoint for asianbetsoccer.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when asianbetsoccer.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 asianbetsoccer.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?+
- Build a live soccer dashboard showing real-time scores and Asian handicap lines across multiple bookmakers.
- Run automated odds-alert pipelines that trigger when
euro1_cudrops below a defined threshold for a specific league. - Aggregate pre-match odds for today and tomorrow using
get_next_gameswithday_offset0 and 1. - Compare Asian handicap lines across Bet365, Sbobet, and AvgOdds for the same match using repeated
get_livescorecalls. - Populate a league selector UI from
get_available_leaguesto scope odds monitoring to a single championship. - Track line movement by polling
get_livescoreat intervals and storing theoddsblock with each timestamp. - Filter in-play matches to a specific handicap line (e.g.
-0.5) usingmonitor_odds_alertswith thehandicapparameter.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does asianbetsoccer.com have an official developer API?+
What does the `monitor_odds_alerts` endpoint actually return, and how does the filtering work?+
handicap (exact line match, e.g. -1.25), championship (case-insensitive substring against the league name), and odds_threshold (matches are included only when their euro1_cu value is below the number you provide). The response includes a criteria object echoing your inputs, a checked_at UTC timestamp, and an alerts_found array with one object per qualifying match containing match, league, euro1, handicap, time, and score.Does the API cover historical match results or odds history?+
get_livescore and upcoming fixtures via get_next_games; there are no endpoints for past results or historical odds series. You can fork it on Parse and revise to add a historical data endpoint if that coverage exists on the source site.Are all eight bookmakers available for both live and upcoming matches?+
bookmaker parameter and the same eight accepted values (188Bet, Bet365, Sbobet, Crown, 12Bet, 18Bet, AvgOdds, Bet365 Live) apply to both get_livescore and get_next_games. However, individual bookmakers may not price every fixture, so some matches may return sparse or absent odds for a given book. get_available_bookmakers lists the full supported set along with each book's internal identifier.Is there a way to retrieve odds for a specific match by ID rather than scanning all live matches?+
get_livescore and get_next_games rather than single-match lookups by ID. The id field is present in response objects and can be used to filter client-side after retrieval. You can fork it on Parse and revise to add a single-match endpoint if targeted lookups are important for your use case.