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:
- Plugged in + idle (
boost_state=available): immediately signals the running schedule workflow to start charging now, bypassing optimization. - Unplugged (
boost_state=unavailabledue to not plugged in): armsboost_for_next_session=True. The next plug-in’s session workflow will automatically fire boost on its schedule child, then auto-reset the flag. - Already charging or in flight (
boost_stateisongoingorrequested): 409 withreason=already_charging. - Fully charged: 409 with
reason=fully_charged. - Feature disabled for this EV’s owning member/org: 409 with
reason=feature_disabled.
Returns 204 on success (boost triggered or armed). Returns 409 when the request can’t be honoured, with fields:
state: the EV’s currentboost_state.reason:already_charging,fully_charged,feature_disabled,no_active_session, orinternal_error.
The arm path is idempotent: re-tapping while already armed returns 204 with
no change. To clear an armed flag, use DELETE /boost.
POST
Trigger a boost charge or arm boost for the next session
Documentation Index
Fetch the complete documentation index at: https://developers.podero.com/llms.txt
Use this file to discover all available pages before exploring further.
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
Previous
Disarm a previously-armed boost for the next sessionClear ``boost_for_next_session`` on the EV.
Idempotent: 204 whether the flag was set or already clear. Use this when
a user taps a button that's currently in the "armed" state to reverse
their pre-plug arming.
Has no effect on a live boost in progress — those end via the natural
end-conditions (full / unplug / OEM stop). To stop a live boost, the
user must unplug the vehicle.
Next
Trigger a boost charge or arm boost for the next session