Log inTalk to us

Migration portal

Migration workspaces: one migration of a project's chargers from a previous platform, for the teams working on it. Open one on the project (stations:admin), list yours (/v1/me/migrations) and read it, import the network into it (/v1/migrations/{migration_id}/imports: the project's network import, whose applied stations join the migration as imported), its chargers (the state board: imported, proxied, shadow, moved, rolling_back, rolled_back, filtered by state, site or job, and each charger's state history), its jobs and its audit log under /v1/migrations/{migration_id}. Roll chargers back by charger, site or all as one job: the charger proxy applies each rollback within seconds, and above 50 chargers socket closes are paced. Roles: client (the project team's owners and admins), Ivora support (on every migration), partner and observer. The client invites partner (or installer) and observer teams by team ID or email, optionally narrowed to some sites; invitees accept at /v1/me/migration-invites for a team they own or administer or a new one, and see that migration and nothing else of the project. A partner rolls back the chargers its own team moved and reads the redacted OCPP log of the migration's chargers. A participant team's owners and admins make team migration keys (migration:* scopes within their own role, shown once) for the Ivora CLI and partner integrations: a key works on its migration's routes only, capped on every request by its creator's current role, and every project route refuses it. The charger proxy's sync agent holds a runner credential (scope migration:routes, shown once) and long-polls the desired routes, reports outcomes and sends heartbeats. The pilot rollback routes under /v1/tenants/{tenant_id}/migration act on the same rollbacks.

52 endpoints