EMP Integration

An E-Mobility Provider (EMP) is a service provider for end-user drivers. You manage customer relationships, issue charging tokens, and provide access to a network of CPO partners.

Architecture

Driver App  ──→  Your Backend  ──→  Agent API  ──→  EV Suite  ──→  CPOs
                                   (REST/JSON)     (OCPI 2.2)

Your app handles the driver-facing experience. Your backend calls the Agent API to search for chargers and create bookings on behalf of drivers.

Key Concepts

Tokens

Each driver has a charging token — either an RFID card or a virtual app token. When you create a booking with the driver_token strategy, EV Suite uses the driver's existing token. The token is synced to CPOs via OCPI, so the driver can tap the same RFID card at the charger.

Multi-CPO Search

When your driver searches for chargers, the Agent API queries all connected CPOs in parallel and returns unified, distance-sorted results. You get real-time availability across the entire network in a single call.

Booking Lifecycle

REQUESTED → PENDING → CONFIRMED → ATTENDING → COMPLETED
                 ↓         ↓
              EXPIRED   CANCELLED / NO_SHOW

• REQUESTED: You submitted the booking, being processed
• PENDING: Sent to CPO, awaiting confirmation
• CONFIRMED: CPO confirmed — driver can go to the charger
• ATTENDING: Vehicle detected at the charger
• COMPLETED: Charging session finished

Token Strategies for EMPs

Strategy	When to Use
driver_token	Driver has a personal RFID or app token (most common for EMPs)
ad_hoc	Guest charging — no pre-existing driver account

Getting Started

1. Search → Book Flow — Complete walkthrough with driver_token
2. Guest Charging — Temporary tokens for contractors or guests
3. Code Examples — Copy-paste samples in 4 languages