> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ionage.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Request a remote charging session

> Validates the driver, connector, fleet contract, billing source, and restrictions before dispatching remote start.



## OpenAPI

````yaml /api-reference/flo/flo-api-oas.json post /public/fleets/v1/sessions
openapi: 3.0.3
info:
  title: FLO Partner API
  version: 1.0.0
  description: >
    Contract-first API for fleet partners building an operations dashboard, a
    driver app,

    or a backend-for-frontend integration with FLO.


    The API is fleet scoped. The API key identifies exactly one fleet; callers
    never send an

    internal fleet ID. Stable opaque public IDs must be persisted instead of
    database IDs,

    phone numbers, or registration numbers.


    Modules:

    - Stations: contracted charging stations, availability, and tariffs.

    - Drivers: app-charging driver onboarding and access management.

    - Vehicles: fleet vehicle registry for tracking and restriction
    configuration.

    - Payments: read-only fleet billing summary and payment transactions.

    - Sessions: asynchronous remote start, observation, and stop for fleet
    drivers.

    - Restrictions: connector-level access, time, and SOC policy.


    Mutation requests that create sessions or resources require an

    Idempotency-Key. Money uses integer paise. A 202 session response means

    the command was accepted for processing, not completed by the charge point.


    Compatibility caveats:

    - Restrictions are evaluated only when FLO can identify the session as
    belonging to the configured driver_id or vehicle_id.

    - SOC-based stop enforcement depends on the CPO/charger sending usable SOC
    updates for the active session.

    - Time-window and SOC stop enforcement depend on the CPO/charger supporting
    remote stop for the active session path.

    - Vehicle restrictions are stored even when FLO cannot yet identify the
    vehicle during charging; enforcement begins when vehicle identification
    becomes available.

    - If identity, SOC telemetry, or remote stop support is unavailable, FLO
    enforces only the supported parts of a restriction.
servers:
  - url: https://api.ionage.in
security:
  - ApiKeyAuth: []
tags:
  - name: Operators
    description: Charge point operators whose stations are contracted to the fleet.
  - name: Drivers
    description: App-charging driver onboarding and access management.
  - name: Vehicles
    description: Fleet vehicle registry for tracking and restriction configuration.
  - name: Restrictions
    description: Connector-level access, time, and SOC policy.
  - name: Stations
    description: Contracted charging stations, availability, and tariffs.
  - name: Billing
    description: Read-only fleet billing summary.
  - name: Transactions
    description: Read-only fleet payment transactions.
  - name: Sessions
    description: Asynchronous remote start, observation, and stop for fleet drivers.
paths:
  /public/fleets/v1/sessions:
    post:
      tags:
        - Sessions
      summary: Request a remote charging session
      description: >-
        Validates the driver, connector, fleet contract, billing source, and
        restrictions before dispatching remote start.
      operationId: post_sessions
      parameters:
        - name: Idempotency-Key
          in: header
          required: true
          schema:
            type: string
          description: >-
            Client UUID retained for at least 24 hours. Same key and request
            returns the original result; a different request returns 409.
          example: 8b52e548-4e34-4d2c-9b53-c3cb35f95e66
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                driver_id:
                  type: string
                connector_id:
                  type: string
              required:
                - driver_id
                - connector_id
            example:
              driver_id: drv_9df5f4f7b0f64f9e
              connector_id: con_3a7bd3e2360a3d80
      responses:
        '202':
          description: >-
            Start accepted for asynchronous processing. The returned status is
            normally INITIATING or PENDING; poll the returned resource.
          headers:
            Retry-After:
              description: Suggested polling delay in seconds.
              schema:
                type: string
          content:
            application/json:
              schema:
                type: object
                properties:
                  session_id:
                    type: string
                  status:
                    type: string
                  driver_id:
                    type: string
                  station_id:
                    type: string
                  charger_id:
                    type: string
                  connector_id:
                    type: string
                  metering:
                    type: object
                    properties:
                      energy_wh:
                        type: integer
                      power_w:
                        type: string
                        nullable: true
                      state_of_charge_percent:
                        type: string
                        nullable: true
                      sampled_at:
                        type: string
                        nullable: true
                    required:
                      - energy_wh
                      - power_w
                      - state_of_charge_percent
                      - sampled_at
                  billing:
                    type: object
                    properties:
                      billing_type:
                        type: string
                      currency:
                        type: string
                      estimated_cost_paise:
                        type: string
                        nullable: true
                      final_cost_paise:
                        type: string
                        nullable: true
                    required:
                      - billing_type
                      - currency
                      - estimated_cost_paise
                      - final_cost_paise
                  start_time:
                    type: string
                    nullable: true
                  end_time:
                    type: string
                    nullable: true
                  created_at:
                    type: string
                    format: date-time
                  updated_at:
                    type: string
                    format: date-time
                required:
                  - session_id
                  - status
                  - driver_id
                  - station_id
                  - charger_id
                  - connector_id
                  - metering
                  - billing
                  - start_time
                  - end_time
                  - created_at
                  - updated_at
              example:
                session_id: ses_9df5f4f7b0f64f9e
                status: INITIATING
                driver_id: drv_9df5f4f7b0f64f9e
                station_id: st_d1ed2dd3f9ef4b4e
                charger_id: ch_2cf24dba5fb0a30e
                connector_id: con_3a7bd3e2360a3d80
                metering:
                  energy_wh: 0
                  power_w: null
                  state_of_charge_percent: null
                  sampled_at: null
                billing:
                  billing_type: PREPAID
                  currency: INR
                  estimated_cost_paise: null
                  final_cost_paise: null
                start_time: null
                end_time: null
                created_at: '2026-09-17T09:07:42Z'
                updated_at: '2026-09-17T09:07:42Z'
        '400':
          description: The request does not match the operation's input requirements.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: VALIDATION_ERROR
                  message: connector_id is required
        '401':
          description: The API key is missing or invalid.
        '403':
          description: The authenticated fleet is not allowed to perform this action.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: FORBIDDEN
                  message: the authenticated fleet is not allowed to use this connector
        '404':
          description: The resource was not found for the authenticated fleet.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: RESOURCE_NOT_FOUND
                  message: the requested resource was not found
        '409':
          description: >-
            The request conflicts with current state or reuses an
            Idempotency-Key with different input.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: CONFLICTING_RESTRICTION
                  message: the request conflicts with the current resource state
        '422':
          description: >-
            The payload is valid but current domain state prevents execution,
            such as insufficient funds, an unavailable connector, or a driver
            who is not ready for charging.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: INSUFFICIENT_FUNDS
                  message: the fleet prepaid balance has insufficient available funds
        '500':
          description: Unexpected server-side error while processing a valid request.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        type: string
                      message:
                        type: string
                    required:
                      - code
                      - message
                required:
                  - error
              example:
                error:
                  code: INTERNAL_ERROR
                  message: an unexpected error occurred while processing the request
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Fleet-scoped API key. The key identifies exactly one fleet; callers
        never send an internal fleet ID.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.