betano.com 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.
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'
Get list of all available regional Betano sites with their URLs and language codes. Returns static data about 20 regional Betano platforms including Argentina, Brazil, Portugal, Germany, and others.
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": "pt",
"url": "https://www.betano.pt/",
"lang": "pt-PT",
"name": "Portuguese"
},
{
"id": "de",
"url": "https://www.betano.de/",
"lang": "de-DE",
"name": "German"
}
]
},
"status": "success"
}
}About the betano.com 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.
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.
- 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 | 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 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.