Fleet Data APIs

These endpoints allow you to securely access and interact with your fleet’s data, including device info, location updates, and trip history.

API Key Provisioning

  • Go to Developers tabs

  • On Fleet Data API Key click Generate API Key

  • Copy and save the key securely — it will only be shown once

Authorization

All API requests require the API Key in the header:

Authorization: Bearer <your API key>

Devices API

Endpoint

GET https://api.trybeekeeper.ai/v1/devices

Returns a list of all devices in your fleet.

Response Format

{
  "devices": [
    {
      "id": "string",
      "serialNumber": "string",
      "name": "string",
      "description": "string",
      "deviceModel": "string",
      "firmwareVersion": "string",
      "vehiclePlate": "string",
      "imei": "string"
    }
  ]
}

Location API

Endpoint

GET https://api.trybeekeeper.ai/v1/location

Query Params

  • deviceId (required)

Returns the latest known location of the specified device.

Response Format

Trips API

Endpoint

GET https://api.trybeekeeper.ai/v1/trips

Query Params

  • deviceId (required)

  • startDate (required, ISO format)

  • endDate (required, ISO format)

Returns trips taken by a device within a specified date range.

Response Format (truncated for clarity)

Fleet Video Incidents API

Query AI-detected driving events (harsh braking, swerving, speeding, etc.) across your fleet, including video clips and optional sensor data.

Authorization

All API requests require your Fleet Data API Key in the header:

Keys with all scope (the default "Full Access" key) have access automatically. Keys with the aievents scope also have access.

Search Events

Endpoint

POST https://api.trybeekeeper.ai/v1/aievents/search

Request Body (JSON)

  • startDate (required, ISO 8601 datetime) — beginning of the time range

  • endDate (required, ISO 8601 datetime) — end of the time range. Range must be 31 days or less.

  • deviceIds (optional, string array) — filter to specific device IDs

  • types (optional, string array) — filter by event type. See Event Types below.

  • polygon (optional, array of [lon, lat] coordinate pairs) — filter to events within a geographic area. The polygon must be closed (first and last point identical) and must not self-intersect.

  • limit (optional, integer 1–500, default 100) — max events to return

  • offset (optional, integer, default 0) — pagination offset

Example Curl Request

Response Format

Get Event by ID

Endpoint

GET https://api.trybeekeeper.ai/v1/aievents/:id

Query Params

  • includeGnssData (optional, true/false) — include high-frequency GPS data (lat, lon, altitude at millisecond resolution)

  • includeImuData (optional, true/false) — include inertial measurement unit data (accelerometer + gyroscope)

Example Curl Request

Response Format

When includeGnssData=true, the response includes a gnssData array:

When includeImuData=true, the response includes an imuData array:

Rewards API

Lists rewards information for all devices in fleet, for a given reward period. A reward period is a calendar week.

Endpoint

GET https://api.trybeekeeper.ai/v1/hivemapperRewards

Query Params

  • rewardPeriod required. date must be a Monday e.g. 2025-05-12

Returns rewards for your devices in your fleet

Response Format

Last updated