> ## 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.

# 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=unavailable` due to not plugged in): arms
  `boost_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_state` is `ongoing` or `requested`):
  409 with `reason=already_charging`.
- **Fully charged**: 409 with `reason=fully_charged`.

Returns 204 on success (boost triggered or armed). Returns 409 when the
request can't be honoured, with fields:
- `state`: the EV's current `boost_state`.
- `reason`: `already_charging`, `fully_charged`, `no_active_session`, or
  `internal_error`.

The arm path is idempotent: re-tapping while already armed returns 204 with
no change. To clear an armed flag, use ``DELETE /boost``.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json post /api/partners/v2.0/org/{org_id}/users/{user_id}/electric-vehicles/{electric_vehicle_id}/boost
openapi: 3.1.0
info:
  title: Podero Partner API
  version: '2.0'
  description: >-
    This API provides a unified interaction point for Podero's partner
    companies.


    The goal of this API is to give partners easily integratable endpoints that
    don't require extensive software

    development. For this reason, the endpoints focus around user and device
    management, setting of preferences

    and high level device controls.


    While direct control of devices is implemented for special use cases such as
    pause power, we abstract away low level

    direct device steering so developers and partners can focus on delivering
    maximum value to end users.
  termsOfService: https://www.podero.com/terms-and-conditions
servers: []
security: []
paths:
  /api/partners/v2.0/org/{org_id}/users/{user_id}/electric-vehicles/{electric_vehicle_id}/boost:
    post:
      tags:
        - User Electric Vehicles
      summary: Trigger a boost charge or arm boost for the next session
      description: >-
        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=unavailable` due to not plugged in): arms
          `boost_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_state` is `ongoing` or
        `requested`):
          409 with `reason=already_charging`.
        - **Fully charged**: 409 with `reason=fully_charged`.


        Returns 204 on success (boost triggered or armed). Returns 409 when the

        request can't be honoured, with fields:

        - `state`: the EV's current `boost_state`.

        - `reason`: `already_charging`, `fully_charged`, `no_active_session`, or
          `internal_error`.

        The arm path is idempotent: re-tapping while already armed returns 204
        with

        no change. To clear an armed flag, use ``DELETE /boost``.
      operationId: >-
        integrations_api_api_v2_organizations_users_electric_vehicles_router_trigger_ev_boost
      parameters:
        - in: path
          name: org_id
          schema:
            description: The organization ID
            format: uuid
            title: Org Id
            type: string
          required: true
          description: The organization ID
        - in: path
          name: user_id
          schema:
            description: The user ID
            format: uuid
            title: User Id
            type: string
          required: true
          description: The user ID
        - in: path
          name: electric_vehicle_id
          schema:
            description: The electric vehicle ID
            format: uuid
            title: Electric Vehicle Id
            type: string
          required: true
          description: The electric vehicle ID
      responses:
        '204':
          description: No Content
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                additionalProperties: true
                title: Response
                type: object
      security:
        - OAuth2: []
components:
  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        password:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}
        clientCredentials:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}

````