BetsAPI APIbetsapi.com ↗
Retrieve completed match results from the eBasketball H2H GG League (4x5mins) on BetsAPI. Get dates, teams, scores, and paginated history via one endpoint.
What is the BetsAPI API?
This API exposes 1 endpoint — get_results — that returns completed match results from the eBasketball H2H GG League (4x5mins) on BetsAPI. Each response delivers up to 30 matches per page in reverse chronological order, with four data fields per match: date, home team, away team, and final score. Pagination is handled through a simple 1-based page parameter, and the response includes a total_pages count so you can iterate the full historical archive.
curl -X GET 'https://api.parse.bot/scraper/88bd064f-14ec-46b5-b471-f891f1332e53/get_results?page=1' \ -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 betsapi-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: H2H GG League SDK — bounded, re-runnable; every call capped."""
from parse_apis.betsapi_com_api import H2hGgLeague, ParseError
client = H2hGgLeague()
# List recent match results — limit caps TOTAL items fetched across all pages.
for match in client.matches.list(limit=3):
print(match.date, match.home_team, "vs", match.away_team, match.score)
# Grab one match for inspection
result = client.matches.list(limit=1).first()
if result:
print(f"Latest: {result.home_team} vs {result.away_team} -> {result.score}")
# Typed error handling
try:
for m in client.matches.list(limit=2):
print(m.date, m.score)
except ParseError as e:
print(f"Error: {e}")
print("exercised: matches.list")
Retrieve completed match results for the eBasketball H2H GG League (4x5mins). Returns matches in reverse chronological order with date/time, home team, away team, and final score. Results are auto-iterated across pages of 30 matches each.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
{
"type": "object",
"fields": {
"page": "current page number",
"matches": "array of match result objects with date, home_team, away_team, and score",
"total_pages": "total number of available pages"
},
"sample": {
"data": {
"page": 1,
"matches": [
{
"date": "2026-07-31T20:47:00Z",
"score": "47-43",
"away_team": "DAL Mavericks (ADMIRAL)",
"home_team": "CHA Hornets (CONQUEST)"
},
{
"date": "2026-07-31T20:43:00Z",
"score": "53-64",
"away_team": "NY Knicks (RAPTOR)",
"home_team": "OKC Thunder (GRAVITY)"
}
],
"total_pages": 7884
},
"status": "success"
}
}About the BetsAPI API
What the API Returns
The get_results endpoint returns completed match data from the eBasketball H2H GG League (4x5mins) — a virtual basketball competition. Each response object includes a matches array where every entry carries the match date, home_team, away_team, and score. Results are ordered newest-first, making it straightforward to pull the latest completed fixtures without additional sorting.
Pagination
Results are delivered in pages of 30 matches each. The optional page input parameter (integer, 1-based) controls which page is returned. The response also returns the current page number and total_pages, so you can determine how many requests are needed to retrieve the full match history for this league without guessing.
Data Coverage
Coverage is specific to the eBasketball H2H GG League (4x5mins) on BetsAPI. The response focuses on final results — score and participant identity — rather than in-game statistics or pre-match odds. The date field on each match result allows you to build time-series views of team performance or reconstruct league standings from raw score data.
The BetsAPI API is a managed, monitored endpoint for betsapi.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when betsapi.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 betsapi.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?+
- Tracking win/loss records for individual teams in the eBasketball H2H GG League over time
- Building a historical score archive by iterating through all available pages using total_pages
- Computing head-to-head records between two teams using the home_team and away_team fields
- Detecting result patterns by analyzing final score margins across paginated match history
- Feeding completed match data into a betting model that requires recent results for calibration
- Monitoring league activity by polling get_results for new entries since the last recorded date
| 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 BetsAPI have an official developer API?+
What exactly does the get_results endpoint return for each match?+
matches array contains four fields: date (when the match was played), home_team, away_team, and score (the final result). The page-level response also includes the current page number and total_pages so you can paginate through the full archive.Does the API return live or in-progress match data?+
get_results endpoint only returns completed matches. In-progress or upcoming fixtures are not included in the response. You can fork this API on Parse and revise it to add an endpoint targeting live or scheduled matches.