Betano APIbetano.com ↗
Access Betano sports betting data via API. Retrieve 20 regional site listings and detailed event odds and markets by event ID and region.
What is the Betano API?
The Betano API provides structured access to the Betano sports betting platform across 2 endpoints. The get_regions endpoint returns a list of 20 regional Betano sites — covering markets from Argentina and Brazil to Portugal and Germany — each with its URL and language code. The get_event_details endpoint returns odds and betting markets for a specific event, identified by event ID and region.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/2c345e08-8176-4558-9e5d-91a75f8768de/get_regions' \ -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 betano-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: Betano Sports API — list all regional platforms."""
from parse_apis.betano_sports_api import Betano, Region, NotFoundError
client = Betano()
# List all regional Betano platforms — static data, single page.
for region in client.regions.list(limit=5):
print(region.id, region.name, region.url, region.lang)
# Drill-down: grab the first region and inspect its fields.
first = client.regions.list(limit=1).first()
if first:
try:
detail = client.regions.list(limit=20)
print(f"First region: {first.name} at {first.url}")
except NotFoundError as exc:
print(f"Region not found: {exc}")
print("exercised: regions.list")
Returns the complete list of regional Betano platforms worldwide (approximately 20 regions). Each region includes a short identifier, display name, site URL, and BCP-47 language tag. The data is static — it changes only when Betano launches or retires a regional site.
No input parameters required.
{
"type": "object",
"fields": {
"regions": "array of region objects each containing id, name, url, and lang"
},
"sample": {
"data": {
"regions": [
{
"id": "ar_caba",
"url": "https://caba.betano.bet.ar/",
"lang": "es-AR",
"name": "Argentinian Spanish (CABA)"
},
{
"id": "br",
"url": "https://www.betano.bet.br/",
"lang": "pt-BR",
"name": "Brazilian Portuguese"
}
]
},
"status": "success"
}
}About the Betano API
Regional Coverage
The get_regions endpoint takes no inputs and returns a static array of region objects. Each object includes an id, name, url, and lang field, representing one of Betano's 20 active regional platforms. This is the starting point for any workflow that targets a specific country's market — the id value from this response is what you pass as region_id in subsequent calls.
Event Details and Odds
The get_event_details endpoint accepts two required parameters: event_id (the identifier for a specific match or event) and region_id (obtained from get_regions). It returns a data object containing odds and betting market information for that event. This covers both pre-match and live events depending on availability in the targeted region.
Regional Geo-Fencing
Betano operates separate platforms for each country, and access to event data may be subject to regional geo-fencing. Requests for certain region and event combinations may be blocked or return incomplete data depending on where the request originates. The region_id parameter controls which regional platform is queried, so pairing it with the correct event_id for that region is necessary for reliable responses.
The Betano API is a managed, monitored endpoint for betano.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when betano.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 betano.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?+
- Map all active Betano regional sites and their language codes for a multi-market odds aggregator
- Pull live or pre-match betting markets for a specific football event in Brazil using
get_event_details - Build a region comparison tool that queries the same event across multiple
region_idvalues to compare market availability - Monitor which Betano platforms are active and what URLs they use for redirect or deep-link workflows
- Seed a database of Betano regional site metadata using the static output of
get_regions - Integrate Betano odds data into a sports analytics dashboard alongside other bookmakers
| 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 Betano have an official public developer API?+
What does the `get_regions` endpoint actually return?+
id, name, url, and lang. The id is the value you use as region_id in calls to get_event_details. The list covers 20 regional Betano platforms including Argentina, Brazil, Portugal, and Germany, among others.Does the API return sports category listings or match schedules, not just event details?+
get_regions and per-event odds data via get_event_details. Sports category listings, league hierarchies, and match schedule browsing are not exposed as endpoints. You can fork this API on Parse and revise it to add an endpoint that retrieves those listings.What happens if I request event details for a region that geo-fences my request?+
get_event_details endpoint may be blocked or return incomplete data for certain region and event combinations due to Betano's regional geo-fencing. This is a platform-level restriction tied to the region_id and the origin of the request, not a limitation of the API's parameters.