Advanced: External Token Systems (pipelet)
The pipelet strategy is for organizations that manage their own token infrastructure. EV Suite acts as a proxy — you provide the token UID, and EV Suite forwards it to the CPO without creating an internal token record.
When to Use pipelet
- Depot management: Large depots with their own access control systems
- Cloud proxy: Your platform issues and manages tokens independently
- Custom RFID: You have your own RFID provisioning and lifecycle management
How It Works
- Your system manages token UIDs externally (your database, your provisioning)
- When booking, you pass
token_uiddirectly - EV Suite uses this UID when communicating with the CPO
- No EV Suite token record is created — your system is the source of truth
Create a Booking with pipelet
curl -s -X POST https://api.petitmonde.energy/api/v1/client/bookings \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"location_id": "DE-ALG-E999888",
"evse_uid": "DE*ALG*E999888*1",
"reservation_start": "2026-02-10T06:00:00Z",
"reservation_end": "2026-02-10T08:00:00Z",
"external_id": "depot-bay-14-morning",
"token_strategy": "pipelet",
"token_uid": "04A2B3C4D5E6F7"
}' | jq .
Required fields:
token_uid— Your externally-managed token identifier (hex format)- Standard booking fields
Token UID Format
The token_uid should be a valid RFID UID in hex format:
- 4 bytes (8 hex chars):
04A2B3C4 - 7 bytes (14 hex chars):
04A2B3C4D5E6F7 - 10 bytes (20 hex chars):
04A2B3C4D5E6F704A2B3
Responsibilities
With pipelet, you are responsible for:
- Token provisioning and lifecycle
- Ensuring the token UID is valid and active
- Synchronizing token status with CPOs (if needed beyond EV Suite)
- Token revocation and security
EV Suite handles:
- Booking lifecycle (REQUESTED → CONFIRMED → COMPLETED)
- CPO communication via OCPI
- Pricing and billing
Comparison with Other Strategies
| Aspect | driver_token | group_token | ad_hoc | pipelet |
|---|---|---|---|---|
| Token managed by | EV Suite | EV Suite | EV Suite (auto) | You |
| Token record in EV Suite | Yes | Yes | Yes (temporary) | No |
| Requires customer_id | Yes | No | No | No |
| Requires token_uid | No | No | No | Yes |
| Use case | EMP apps | Fleets | Guests | Depots, proxies |