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

# Add a fleet vehicle

> Normalizes the registration number and creates a fleet vehicle record.



## OpenAPI

````yaml /api-reference/flo/flo-api-oas.json post /public/fleets/v1/vehicles
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/vehicles:
    post:
      tags:
        - Vehicles
      summary: Add a fleet vehicle
      description: Normalizes the registration number and creates a fleet vehicle record.
      operationId: post_vehicles
      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:
                registration_number:
                  type: string
              required:
                - registration_number
            example:
              registration_number: KA01AB1234
      responses:
        '201':
          description: Vehicle created.
          content:
            application/json:
              schema:
                type: object
                properties:
                  vehicle_id:
                    type: string
                  registration_number:
                    type: string
                  status:
                    type: string
                required:
                  - vehicle_id
                  - registration_number
                  - status
              example:
                vehicle_id: veh_9df5f4f7b0f64f9e
                registration_number: KA01AB1234
                status: ACTIVE
        '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.
        '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
        '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.