v2.9.0

Released 17th June 2026

This release includes a breaking change: the scheduled value was removed from the execution status field. See Execution Status Cleanup below.

DVIR Log Enhancements

This minor release expands the DVIR log schema with new status tracking and certification fields, giving you richer inspection data across all DVIR log responses.

Backward compatible: The new DVIR fields are additive. No existing DVIR fields have been removed or modified, and no migration is required for them.

Schema Changes

DVIR log — new fields

Three new fields have been added to the BaseDvirLog schema and are reflected in all DVIR log responses, including DvirLogAdded and DvirLogModified webhook payloads.

Field	Type	Description
`status`	`DvirStatusEnum`	Inspection status of the DVIR log.
`certified_by`	`string`	Name of the person who certified the inspection.
`certify_date`	`string`	Date and time the inspection was certified.

Example response (partial):

{
  "id": "dvir_abc123",
  "status": "certified",
  "certified_by": "Jane Smith",
  "certify_date": "2026-06-17T08:30:00Z",
  "certify_comment": "No defects found. Vehicle is safe to operate."
}

New DvirStatusEnum schema

A new DvirStatusEnum schema has been added to the API, representing the possible inspection statuses for a DVIR log. Use the status field on DVIR log responses to determine the current certification state of an inspection.

Affected endpoints

The following endpoints return DVIR log objects and now include the new fields:

GET /v2/telematics/dvir-logs — List DVIR logs
GET /v2/telematics/dvir-logs/{dvir_log_id} — Get a single DVIR log
Webhook payloads for dvir_log.added and dvir_log.modified events

Execution Status Cleanup

This release removes the scheduled value from the ExecutionStatusEnum in the Integrations API. Execution records no longer use this status — consumers filtering or branching on scheduled should update their integration accordingly.

Breaking change: The scheduled enum value has been removed from the status field on execution records. Any code that checks for or handles status === "scheduled" must be updated.

Schema Changes

ExecutionStatusEnum — removed scheduled value

The scheduled value has been removed from the status field returned by:

GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions

Before:

{
  "status": "scheduled" // no longer valid
}

After:The status field will only contain one of the remaining valid values. Remove any handling for "scheduled" from your integration.Migration:

# Before — handled scheduled status
if execution["status"] == "scheduled":
    handle_scheduled(execution)

# After — remove the scheduled branch
# "scheduled" is no longer returned; handle only the remaining statuses

Migration checklist

Audit status handling

Search your codebase for any references to "scheduled" in the context of execution status values and remove or replace them.

Update conditional logic

If you branch on status === "scheduled" to determine whether an execution is pending, use the appropriate remaining status value instead.

Update stored enumerations

If you store or validate execution status values in a database schema, enum type, or configuration, remove scheduled from those definitions.

Fleet TSP Data

This release adds TSP (Telematics Service Provider) association data to fleet analytics responses, giving you richer context about which providers are connected to each fleet.

Backward-compatible addition: All existing integrations continue to work without modification. The new tsps field is additive.

New response fields

Fleet analytics — tsps field

The GET /v2/intelligence/analytics/fleets endpoint now includes a tsps property on each FleetSummary object in the response. This field exposes the TSP connections associated with each fleet, using the new FleetTsp schema.Endpoint: GET /v2/intelligence/analytics/fleetsNew field in response items:

Field	Type	Description
`tsps`	`FleetTsp[]`	List of TSP connections associated with the fleet.

Example response (abbreviated):

{
  "items": [
    {
      "fleet_id": "f1a2b3c4-...",
      "name": "Acme Trucking",
      "tsps": [
        {
          "provider": "samsara",
          "status": "active"
        }
      ]
    }
  ]
}

Schedule Fetch Window End Time

This release adds a new fetch_window_end_at field to schedule and execution objects across the Integrations API, giving you finer control over the time window used when fetching data from telematics service providers.

Backward-compatible addition: This change is additive. No existing fields or endpoints have been removed or modified by it.

New Fields

fetch_window_end_at on schedules and executions

The fetch_window_end_at field is now available on schedule and execution objects. It defines the end boundary of the time window used when fetching data from a TSP during a scheduled run.Affected schemas:

ScheduleRead — returned when reading a schedule
ScheduleCreate — accepted when creating a schedule
ScheduleUpdate — accepted when updating a schedule
ExecutionRead — returned when reading execution history

Affected endpoints:

Method	Endpoint
`GET`	`/v2/integrations/connections/{connection_id}/schedules`
`POST`	`/v2/integrations/connections/{connection_id}/schedules`
`GET`	`/v2/integrations/connections/{connection_id}/schedules/{schedule_id}`
`PATCH`	`/v2/integrations/connections/{connection_id}/schedules/{schedule_id}`
`POST`	`/v2/integrations/connections/{connection_id}/schedules/{schedule_id}/activate`
`POST`	`/v2/integrations/connections/{connection_id}/schedules/activate-schedules`
`GET`	`/v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions`

Example — creating a schedule with a fetch window end time:

POST /v2/integrations/connections/{connection_id}/schedules
Content-Type: application/json

{
  "fetch_window_end_at": "2026-06-17T22:00:00Z"
}

Example — schedule response including the new field:

{
  "id": "sch_abc123",
  "connection_id": "conn_xyz456",
  "fetch_window_end_at": "2026-06-17T22:00:00Z"
}

Overview

Authentication

Telematics

Organizations

Integrations

Notifications

Intelligence

DVIR Log Enhancements

Schema Changes

Affected endpoints

Execution Status Cleanup

Schema Changes

Migration checklist

Fleet TSP Data

New response fields

Schedule Fetch Window End Time

New Fields

Need help?

API reference

Contact support

​DVIR Log Enhancements

​Schema Changes

​Affected endpoints

​Execution Status Cleanup

​Schema Changes

​Migration checklist

​Fleet TSP Data

​New response fields

​Schedule Fetch Window End Time

​New Fields

​Need help?

API reference

Contact support

DVIR Log Enhancements

Schema Changes

Affected endpoints

Execution Status Cleanup

Schema Changes

Migration checklist

Fleet TSP Data

New response fields

Schedule Fetch Window End Time

New Fields

Need help?