Live Google map using the coordinates configured for each published location.
| Charge point | State | Hardware | Last seen |
|---|
Enrol hardware, inspect connectors and issue remote commands.
| Charge point | Status | Connectors / plugs | Vehicle SOC | Hardware | Power / protocol | Price per kWh | Last seen |
|---|
Energy, authorization token and vehicle identity where supplied by the charger.
| ID | Charge point | Connector | Vehicle / ID tag | SOC | Started | Stopped | Energy | Status |
|---|
Manage RFID access and the AutoCharge vehicles registered against each account.
| ID tag | Status | Parent | Vehicles | Expiry | Source |
|---|
Manage account ownership and consent for vehicles authorised to begin charging automatically.
| Vehicle ID | ID tag | Name | Consent | Last seen |
|---|
Compatible vehicle credentials detected by chargers but not currently linked to an account.
| Vehicle ID | Charge point | Previous ID tag | Last detected | State |
|---|
Select a marker to see its location card and connected charge points.
Create individual accounts and manage their roles and login credentials.
| Username | Role | Created |
|---|
Create airport and fire-crew accounts, then control which chargers and ID tags each manager can access.
| Username | Assigned chargers | Managed ID tags | Created |
|---|
—ocpp1.6——Register multiple eMSPs using either provider-initiated or Aerovolt-initiated credential exchange.
—| Provider | OCPI party | Protocol | Registration | Role / status | Allowed IPs | Last activity |
|---|
Send Authorization: Bearer <API_KEY> with every request.
| Method | Endpoint | Purpose |
|---|