asianbetsoccer.com APIasianbetsoccer.com ↗
Access live soccer scores, Asian handicap odds, upcoming match schedules, and bookmaker listings from asianbetsoccer.com via 5 structured API endpoints.
curl -X GET 'https://api.parse.bot/scraper/722cb732-6512-4ace-9466-bb35e4ae5227/get_livescore?bookmaker=188Bet' \ -H 'X-API-Key: $PARSE_API_KEY'
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.
| Param | Type | Description |
|---|---|---|
| bookmaker | string | Bookmaker name. Accepted values: 188Bet, Bet365, Sbobet, Crown, 12Bet, 18Bet, AvgOdds, Bet365 Live. |
{
"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": "109",
"euro1_cu": "1.36",
"euro2_cu": "6.60",
"euroX_cu": "4.60",
"a_odds_cu": "1.98",
"h_line_cu": "-1.25",
"h_odds_cu": "1.90",
"ou_line_cu": "2.75",
"over_odds_cu": "1.94",
"under_odds_cu": "1.92"
},
"league": "Copa Libertadores",
"status": "live",
"away_team": "Cusco FC",
"home_team": "Dep.Independiente Medellin",
"match_time": "2'",
"score_away": "0",
"score_home": "0"
}
]
},
"status": "success"
}
}About the asianbetsoccer.com 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.
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.
- 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 | 250 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.