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

# List charging restrictions



## OpenAPI

````yaml /api-reference/flo/flo-api-oas.json get /public/fleets/v1/restrictions
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/restrictions:
    get:
      tags:
        - Restrictions
      summary: List charging restrictions
      operationId: get_restrictions
      parameters:
        - name: driver_id
          in: query
          required: false
          schema:
            type: string
          description: Stable FLO fleet driver identifier.
          example: drv_9df5f4f7b0f64f9e
        - name: vehicle_id
          in: query
          required: false
          schema:
            type: string
          example: veh_9df5f4f7b0f64f9e
        - name: connector_id
          in: query
          required: false
          schema:
            type: string
          example: con_3a7bd3e2360a3d80
        - name: limit
          in: query
          required: false
          schema:
            type: integer
          example: 50
        - name: offset
          in: query
          required: false
          schema:
            type: integer
          example: 0
      responses:
        '200':
          description: Charging restrictions.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        restriction_id:
                          type: string
                        created_at:
                          type: string
                          format: date-time
                        updated_at:
                          type: string
                          format: date-time
                        vehicle_id:
                          type: integer
                      required:
                        - restriction_id
                        - created_at
                        - updated_at
                        - vehicle_id
                  metadata:
                    type: object
                    properties:
                      total_count:
                        type: integer
                      next:
                        type: string
                      prev:
                        type: string
                        nullable: true
                    required:
                      - total_count
                      - next
                      - prev
                required:
                  - data
                  - metadata
              example:
                data:
                  - restriction_id: res_7d793037a0760186
                    created_at: '2020-07-24T17:07:12.787Z'
                    updated_at: '1950-12-15T09:41:52.192Z'
                    vehicle_id: 3033
                  - restriction_id: res_7d793037a0760186
                    created_at: '2000-05-04T19:13:13.589Z'
                    updated_at: '1963-07-17T07:02:43.211Z'
                    vehicle_id: 1534
                metadata:
                  total_count: 125
                  next: /public/fleets/v1/restrictions?limit=50&offset=50
                  prev: null
        '401':
          description: The API key is missing or invalid.
        '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.