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

> ## Agent Instructions
> Nash exposes two MCP servers. The docs MCP server at https://docs.usenash.com/mcp searches this documentation and needs no credentials. The Nash MCP server at https://mcp.usenash.com/mcp operates an organization's deliveries and needs a Nash API key. See https://docs.usenash.com/reference/build-with-ai.
> Use the Sandbox environment (https://api.sandbox.usenash.com/v1) for anything that creates or dispatches deliveries during development.

# List Driver Groups

> List the driver groups in your internal fleet, newest first.

Use this to read the driver groups your organization has, with the stable `firstVersionContractId` each one is known by. Disabled groups are left out unless you send `activeOnly=false`.

Results come back newest first, up to 500 a page. Pass the `nextCursor` from one page as `cursor` on the next call; a missing `nextCursor` means you've reached the end. To read who is in a group, call [Get Driver Group](/api-reference/fleet/get-driver-group).


## OpenAPI

````yaml get /v1/fleet/driver-groups
openapi: 3.1.0
info:
  title: Nash API
  version: 1.0.0
servers:
  - url: https://api.sandbox.usenash.com
    description: Sandbox API
  - url: https://api.sandbox.ap-southeast-2.usenash.com
    description: Sandbox API (Australia)
  - url: https://api.usenash.com
    description: Production API
  - url: https://api.ap-southeast-2.usenash.com
    description: Production API (Australia)
security: []
tags:
  - name: Notifications
    description: Notifications
    x-nash-topic: config
  - name: Annotate
    description: Annotate
    x-nash-topic: wismo
  - name: Notifications — Send
    description: One-off notification send without a NotificationTrigger.
    x-nash-topic: notifications
  - name: Shipping
    description: Shipping operations
    x-nash-topic: shipping
  - name: Workflow
    description: Workflow automation management
    x-nash-topic: scheduling
  - name: Workflow Execution
    description: Workflow execution history and monitoring
    x-nash-topic: scheduling
  - name: Optimization Strategies
    description: Create, read, update, and delete route optimization strategies.
    x-nash-topic: scheduling
  - name: AI Agents
    description: AI agent management — create, read, update, and delete agents
    x-nash-topic: config
  - name: AI Functions
    description: LLM-backed domain tools
    x-nash-topic: ai
  - name: Webhooks
    description: Webhook delivery inspection
    x-nash-topic: webhooks
  - name: Miscellaneous
    description: Miscellaneous
  - name: Job
    description: Job
    x-nash-topic: wismo
  - name: Batch Job
    description: Batch Job
    x-nash-topic: wismo
  - name: Order
    description: Order
    x-nash-topic: wismo
  - name: Provider
    description: Provider
    x-nash-topic: provider
  - name: Dispatch Strategies
    description: Dispatch Strategies
    x-nash-topic: scheduling
  - name: Store Locations
    description: Store Locations
    x-nash-topic: config
  - name: Delivery Windows
    description: Delivery Windows
    x-nash-topic: config
  - name: Templates
    description: Templates
    x-nash-topic: config
  - name: Zones
    description: Zones
    x-nash-topic: config
  - name: Feedback
    description: Feedback
    x-nash-topic: reporting
  - name: Organizations
    description: Organizations
    x-nash-topic: config
  - name: Store Catalog
    description: Store Catalog
    x-nash-topic: config
  - name: Route
    description: Route
    x-nash-topic: scheduling
  - name: Messaging
    description: Messaging
    x-nash-topic: config
  - name: Billing
    description: Invoice-aligned customer billing usage
    x-nash-topic: config
  - name: Contracts
    description: Provider contract pricing and version listings
    x-nash-topic: provider
  - name: Couriers
    description: Couriers
    x-nash-topic: provider
  - name: Fleet
    description: >-
      Inbound endpoints fleets call to manage their drivers and update in-flight
      deliveries.
    x-nash-topic: driver
  - name: Embed Sessions
    description: >-
      Mint short-lived, browser-safe sessions for embedded Nash Widgets.
      Authenticated with an org embed credential, which must stay on your
      backend.
    x-nash-topic: config
  - name: Event Timeline
    description: Entity-scoped event timeline + outbound provider traffic for one entity.
    x-nash-topic: internal
  - name: Optimization Fleet Projection
    description: >-
      Optimizer-facing projection of the effective fleet for a single-store
      solve
    x-nash-topic: scheduling
  - name: Hub Scanning
    description: Scan physical packages onto their route rack at a hub.
    x-nash-topic: scheduling
  - name: Inventory
    description: Store inventory catalog sync to SFTP retail destinations (e.g. Uber).
    x-nash-topic: store_catalog
  - name: Optimization Activities
    description: Optimization runs launched from the portal or the API
    x-nash-topic: scheduling
  - name: Route Restrictions
    description: Org-scoped geographic areas the route optimizer must avoid traversing.
    x-nash-topic: config
  - name: Shifts
    description: Shifts
    x-nash-topic: provider
  - name: Users
    description: User, role, and organization-membership management.
    x-nash-topic: config
  - name: Vehicles
    description: Vehicles
    x-nash-topic: provider
  - name: Widgets
    description: >-
      Org configuration for embedded Nash Widgets: parent origins, enablement,
      and embed credentials.
    x-nash-topic: config
  - name: Provider Chat
    description: Carrier-chat context for a route, scoped to the caller's organization.
    x-nash-topic: internal
  - name: Order Ingestion
    description: >-
      Internal validate, commit, and reconciliation boundary for governed Order
      imports.
    x-nash-topic: internal
paths:
  /v1/fleet/driver-groups:
    get:
      tags:
        - Fleet
      summary: List Driver Groups
      description: >-
        List the driver groups in your internal fleet. Only active groups are
        returned unless `activeOnly=false`. Supports keyset pagination via the
        cursor returned in `nextCursor`, ordered by original group creation time
        and stable group ID, newest first. Each page returns the latest group
        data; versioning a group does not change its paging position. Pages are
        live reads, so newly created groups or changes to visibility may require
        a new pass.
      operationId: driver_groups_v1_list_driver_groups_route_get
      parameters:
        - name: activeOnly
          in: query
          required: false
          schema:
            title: Activeonly
            type: boolean
            default: true
        - name: limit
          in: query
          required: false
          schema:
            title: Limit
            maximum: 500
            minimum: 1
            type: integer
            default: 100
        - name: cursor
          in: query
          required: false
          schema:
            title: Cursor
            anyOf:
              - type: string
              - type: 'null'
            default: null
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListDriverGroupsResponse'
        '422':
          description: Unprocessable Content
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/NashValidationError'
components:
  schemas:
    ListDriverGroupsResponse:
      title: ListDriverGroupsResponse
      required:
        - driverGroups
      type: object
      properties:
        driverGroups:
          title: Drivergroups
          type: array
          items:
            $ref: '#/components/schemas/DriverGroupRead'
        nextCursor:
          title: Nextcursor
          anyOf:
            - type: string
            - type: 'null'
          default: null
    NashValidationError:
      title: NashValidationError
      required:
        - error
        - response_status
        - RequestID
      type: object
      properties:
        error:
          $ref: '#/components/schemas/NashErrorDetails'
        response_status:
          title: Response Status
          type: string
        RequestID:
          title: Requestid
          type: string
    DriverGroupRead:
      title: DriverGroupRead
      required:
        - firstVersionContractId
        - displayName
        - isActive
        - providerId
      type: object
      properties:
        firstVersionContractId:
          title: Firstversioncontractid
          type: string
          description: Stable id of the driver group across versions.
        externalIdentifier:
          title: Externalidentifier
          anyOf:
            - type: string
            - type: 'null'
          default: null
        displayName:
          title: Displayname
          type: string
        isActive:
          title: Isactive
          type: boolean
        unassignedDriverTimeoutMinutes:
          title: Unassigneddrivertimeoutminutes
          anyOf:
            - type: integer
            - type: 'null'
          default: null
        providerId:
          title: Providerid
          type: string
    NashErrorDetails:
      title: NashErrorDetails
      required:
        - code
        - message
      type: object
      properties:
        code:
          title: Code
          type: string
        message:
          title: Message
          type: string
        details:
          title: Details
          anyOf:
            - type: object
              additionalProperties: true
            - type: 'null'
          description: >-
            Structured error context; shape depends on `code`. For
            `VALIDATION_ERRORS` (HTTP 422) it is `{"fields": [{"loc": [...],
            "msg": "...", "type": "..."}]}` — one entry per invalid field, where
            `loc` is the field path, `msg` the human-readable message, and
            `type` the machine-readable error type (e.g. `string_type`,
            `missing`).
          default: null

````

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