Build with the Ivora API
Manage charging inventory, operate chargers and build payment experiences through one tenant-scoped API. Your application owns its users, bookings and business rules. Ivora supplies charging operations and metering, with optional payment adapters.
Important
This reference describes production at https://api.ivoracharge.com. During
launch, access is limited to Ivora staff and approved tenants, and Ivora grants it
explicitly. Ivora-managed Stripe payments are live card payments charged
directly on each tenant's own Stripe account; Ivora enables them per environment
and each tenant's account is reviewed first. Production does not yet enable
charger display updates, and it does not offer custom OCPP domains or the
existing driver checkout routes. Each settlement guide states what is available
and what is proposed.
Pick your starting point
| I want to… | Start here |
|---|---|
| Make my first authenticated request | Quickstart |
| Understand the API cutover boundary | Charger management and billing support |
| Register or operate a charger | Inventory and commands |
| Keep a charger connected and diagnosable | Connecting chargers |
| Connect chargers on my own domain | Custom OCPP domains |
| Show a payment QR on a charger screen | Charger displays |
| Show the running cost on a charger screen (California CTEP) | Running cost |
| Choose who handles payments | Compare settlement flows |
| Take card payments on my Stripe account | Payment account |
| Integrate my own payment processor | Application-managed payments and Payment integration |
| Get notified instead of polling | Webhooks and events |
| Test an endpoint interactively | API reference |
| Give an AI agent API context | Agent integration |
Diagram source
flowchart TD
App[Your application backend] --> Access[Ivora tenant API]
Access --> Inventory[Inventory and charger control]
Inventory --> Usage[Metered transactions]
Usage --> Bills[Tariffs and bills]
Bills --> Managed[Ivora payment adapter]
App --> External[Your payment processor]
External -->|External sessions and optional reports| BillsThese paths represent existing API components. The Ivora Stripe adapter takes live payments only where Ivora has enabled it and the tenant's payment account is active. External processors remain in your backend; reports do not move money or independently verify payment. See the external workflow and limits.