Read whether the project uses per-project charger URLs (not available in production)
get/v1/tenants/{tenant_id}/charger-urls
Requires an API key
enabled: the project's chargers may be registered with charger_id and connect at connection_base_url followed by their charger ID; source: whether that is the environment's default or an Ivora staff override (changed by staff only, PUT /v1/admin/tenants/{tenant_id}/charger-urls). Requires stations:read, or the project's charger proxy key (migration:proxy). Read-only.
Path parameters
- tenant_idintegerRequired
Returns · 200
- tenant_idintegerRequired
- availablebooleanRequiredThis environment serves per-project charger URLs; when false, enabling answers 409 project_urls_unavailable.
- enabledbooleanRequiredThe effective state: on by default where available, unless staff turned it off.
- sourceenumRequireddefault: no staff override, enabled is the environment's default; override: staff set enabled.One of
default,override - connection_base_urlstring | nullRequiredAlways null in production, where per-project charger URLs are not available.
- updated_bystring | nullRequired
- updated_atstring | nullRequired
GET /v1/tenants/{tenant_id}/charger-urls
curl --fail-with-body "https://api.ivoracharge.com/v1/tenants/1042/charger-urls" \
-H "Authorization: Bearer $IVORA_API_KEY"Response · 200JSON
{
"tenant_id": 1042,
"available": false,
"enabled": false,
"source": "default",
"connection_base_url": "https://app.example.com/return",
"updated_by": "string",
"updated_at": "2026-09-30T17:00:00Z"
}Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com
Paste a production api key (iv_live_…). Create keys in Developer tools. The key stays in this page's memory, is sent only to https://api.ivoracharge.com and clears when you reload. Test keys are refused.



