User Electric Vehicles
Trigger a boost charge or arm boost for the next session
Trigger boost on the EV.
Behaviour depends on the EV’s current state (boost_state):
- Not steered (the EV is unauthenticated, or runs no optimization mode a boost
could override): 409
steering_inactive.boost_feature_enabledis False on the EV payload for exactly these devices, so the button is not offered. - Plugged, boostable (
available— idle OR charging normally as part of optimization): immediately signals the running schedule workflow to boost now, overriding optimization. When no session run covers the plug-in, the tap opens the session from the car’s latest plugged reading and the boost fires as the session starts. - Unplugged (
unavailable): armsboost_for_next_session=True. The next plug-in’s session workflow fires boost on its schedule child, then auto-resets. - A boost already running (
ongoingorrequested): 409already_charging. - Cancel in flight (
stopping): un-cancels the live boost, returning toongoing.
Returns 204 on success (boost triggered, un-cancelled, or armed). Returns 409 when the request can’t be honoured, with fields:
state: the EV’s currentboost_state.reason:steering_inactive,already_charging,no_active_session, orinternal_error.
The arm path is idempotent: re-tapping while already armed returns 204 with
no change. To cancel a live boost or clear an armed flag, use DELETE /boost.
POST
Trigger a boost charge or arm boost for the next session
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID
The user ID
The electric vehicle ID
Response
No Content
