Go Fleet Vision API Documentation.

How to Create an API Key

API keys are generated from your Go Fleet Vision company dashboard. Only the main company account has the ability to create API keys. These keys enable third-party integrations to access your units' tracking data.

Step-by-step instructions

1. 1

   Log In

   Access your Go Fleet Vision account by logging in with your main company account credentials at the dashboard.

2. 2

   Navigate to API Keys

   In the sidebar, scroll down to the "More" section. Click on API Keys to open the API key management page.

3. 3

   Add a New Key

   Click the 'Add Key' button to initiate the creation process.

4. 4

   Configure & Generate

   Provide a descriptive title for your key (for identification purposes), then click 'Generate' to produce the API key.

5. 5

   Copy & Use

   Copy the generated key and store it securely. Use it in API requests via the x-api-key header for third-party integrations.

Key details

Drivers

This API provides real-time driver data access, allowing partners to retrieve active or inactive drivers and paginate through large lists.

GET https://read.gofleetvision.com/api/externalservice/drivers-list/:usdot?page={page}&perPage={perPage}&is_active={boolean}

Parameters

Response

Returns driver records plus pagination metadata. The data array contains driver objects, and meta provides pagination info.

{
  "data": [
    {
      "id": "string(uuid)",
      "first_name": "string",
      "second_name": "string"
    }
  ],
  "meta": {
    "page": 1,
    "perPage": 10,
    "total": 100,
    "totalPages": 10
  }
}

Example cURL request

curl --location 'https://read.gofleetvision.com/api/externalservice/drivers-list/123456?page=1&perPage=10&is_active=true' \
--header 'x-api-key: <your-api-key>' \
--header 'provider-token: <your-provider-token>'

Trucks

This API provides real-time access to unit assignments, enabling partners to view truck assignments alongside driver and co-driver details.

GET https://read.gofleetvision.com/api/externalservice/current-units/:usdot

Parameters

GET https://read.gofleetvision.com/api/externalservice/current-units/123456?page=1&perPage=10&is_active=true

Response

Returns an array of unit objects with their assigned driver and co-driver information, along with pagination metadata.

{
  "data": [
    {
      "id": "string(uuid)",
      "vin": "string",
      "truck_number": "string",
      "driver": {
        "id": "string",
        "first_name": "string",
        "second_name": "string"
      },
      "codriver": {
        "id": "string",
        "first_name": "string",
        "second_name": "string"
      }
    }
  ],
  "meta": {
    "page": 1,
    "perPage": 10,
    "total": 100,
    "totalPages": 10
  }
}

Example cURL request

curl --location 'https://read.gofleetvision.com/api/externalservice/current-units/123456?page=1&perPage=10&is_active=true' \
--header 'x-api-key: <your-api-key>' \
--header 'provider-token: <your-provider-token>'

Trackings

Provides access to historical vehicle tracking data by date range. Returns a chronological array of telemetry objects for the specified vehicle.

GET https://read.gofleetvision.com/api/externalservice/trackings/:usdot/:vehicleId/?from={date}&to={date}

Parameters

Response

Returns a chronological array of telemetry objects. Each object contains the vehicle's location, speed, heading, driver, odometer reading, and timestamp.

[
  {
    "address": "string",
    "coordinates": {
      "lat": 0.0,
      "lng": 0.0
    },
    "rotation": 0,
    "speed": 0,
    "driverId": "string",
    "odometer": 0,
    "date": "2026-01-10T08:32:11.000Z"
  }
]

Example cURL request

curl --location 'https://read.gofleetvision.com/api/externalservice/trackings/123456/<vehicleId>/?from=2026-01-10T00:00:00.000Z&to=2026-01-13T00:00:00.000Z' \
--header 'x-api-key: <your-api-key>' \
--header 'provider-token: <your-provider-token>'

Data is returned in chronological order.

Historical Active Units

Enables partners to identify vehicles that were active within a requested date range.

GET https://read.gofleetvision.com/api/externalservice/active-units/:usdot/?from={date}&to={date}

Parameters

GET https://read.gofleetvision.com/api/externalservice/active-units/123456/?from=2026-01-10T00:00:00.000Z&to=2026-01-13T00:00:00.000Z

Response

Returns an array of unit objects for all vehicles that were active within the requested time range.

[
  {
    "id": "string",
    "truck_number": "string",
    "vin": "string"
  }
]

Example cURL request

curl --location 'https://read.gofleetvision.com/api/externalservice/active-units/123456/?from=2026-01-10T00:00:00.000Z&to=2026-01-13T00:00:00.000Z' \
--header 'x-api-key: <your-api-key>' \
--header 'provider-token: <your-provider-token>'

Tracking API (v2)

Provides real-time vehicle tracking data including location, unit number, VIN, and timestamp for all units associated with a USDOT number.

GET https://read.gofleetvision.com/api/v2/units-by-usdot/:usdot

Parameters

Response

Returns a units array containing the current tracking data for all vehicles under the specified USDOT.

{
  "units": [
    {
      "truck_number": "string",
      "vin": "string",
      "coordinates": {
        "lat": 0.0,
        "lng": 0.0
      },
      "timestamp": "2026-01-10T08:32:11.000Z"
    }
  ]
}

Example cURL request

curl --location --request GET \
  'https://read.gofleetvision.com/api/v2/units-by-usdot/123456' \
  --header 'x-api-key: <your_key>' \
  --header 'provider-token: <your_token>'

Tracking by VIN Number API (v2)

This endpoint delivers real-time vehicle tracking data by VIN number, including location, unit number, and related details.

GET https://read.gofleetvision.com/api/v2/unit-by-vin/:usdot/:vin

Parameters

Response

Returns a unit object with the current real-time tracking data for the specified vehicle.

{
  "unit": {
    "truck_number": "string",
    "vin": "string",
    "coordinates": {
      "lat": 0.0,
      "lng": 0.0
    },
    "timestamp": "2026-01-10T08:32:11.000Z"
  }
}

Example cURL request

curl --location --request GET \
  'https://read.gofleetvision.com/api/v2/unit-by-vin/0/4V4NC9EG0FN911517' \
  --header 'x-api-key: <your-api-key>' \
  --header 'provider-token: <your-provider-token>'

:usdot and :vin are URL path parameters. A legacy endpoint path (/api/unit-by-vin/) also exists in some documentation examples.