Each BentoCal application lives in one region. Its users' connections, tokens and event links are stored and processed there, and the application is served from that region's base URL:
https://api.bentocal.com/{region}/v1Available regions
| Region | Code | Base URL |
|---|---|---|
| Australia | au | https://api.bentocal.com/au/v1 |
Europe (eu) and the United States (us) are planned.
You choose the region when you create an application, and it can't be changed later. To serve users in several regions, create one application per region.
Find your base URL
Your application's Overview tab in the console shows its API base URL and a ready-to-run curl example.
Region-specific URLs
Everything an application uses lives under its region:
| What | URL |
|---|---|
| REST API | https://api.bentocal.com/{region}/v1/… |
| Hosted connect page | https://api.bentocal.com/{region}/connect/{connect_session_id}, returned as url when you create a connect session |
| Microsoft admin consent page | https://api.bentocal.com/{region}/admin-consent/{application_id}, shown on the Admin consent tab |
Wrong region
API keys carry their region (bc_test_au_…). A key sent to another region's base URL gets 400 wrong_region, so a misconfigured base URL fails fast instead of looking like a missing user.
OpenAPI document
The API is described by an OpenAPI 3.1 document at https://api.bentocal.com/openapi.json. Its servers entry takes the region as a variable. Use it to generate a client or import the API into tools like Postman. The API reference is built from the same document.