table.supported-providers {
  width: 100%;
  display: unset;
}

p:has(> table.supported-providers.sticky-header) {
  height: 600px;
  overflow: auto;
}

table.supported-providers.sticky-header thead tr {
  top: 0;
  position: sticky;
  z-index: 3;
  background-color: #fff;
}

.dark table.supported-providers.sticky-header thead tr {
  background-color: rgb(var(--background-dark));
}

table.supported-providers th {
  white-space: nowrap;
}

table.supported-providers td {
  white-space: normal;
  word-wrap: break-word;
  overflow: hidden;
  text-overflow: ellipsis;
}

@media (max-width: 640px) {
  table.supported-providers td {
    max-width: 200px;
  }
}

@media (min-width: 641px) and (max-width: 1024px) {
  table.supported-providers td {
    max-width: 300px;
  }
}

@media (min-width: 1025px) {
  table.supported-providers td {
    max-width: 600px;
  }
}

table.supported-providers thead th::after {
  content: '';
  position: absolute;
  left: 0;
  bottom: -1px; /* Adjust this if the scrollbar width is an issue */
  right: 0;
  height: 1px;
  background-color: #ddd;
}

.dark table.supported-providers thead th::after {
  background-color: rgb(var(--background-dark));
}

table.supported-providers th:first-of-type,
table.supported-providers td:first-of-type {
  min-width: 230px;
  position: sticky;
  left: 0;
  background-color: #fff;
  z-index: 2;
  text-align: left;
  margin-right: 1rem;
}

.dark table.supported-providers th:first-of-type,
.dark table.supported-providers td:first-of-type {
  background-color: rgb(var(--background-dark));
}

table.supported-providers th.center-text,
table.supported-providers td.center-text {
  text-align: center;
}

table.supported-providers th:first-of-type::after,
table.supported-providers td:first-of-type::after {
  content: '';
  position: absolute;
  top: 0;
  right: -1px; /* Adjust this if the scrollbar width is an issue */
  bottom: 0;
  width: 1px;
  background-color: #ddd;
}

.dark table.supported-providers th:first-of-type::after,
.dark table.supported-providers td:first-of-type::after {
  background-color: rgb(var(--background-dark));
}

table.supported-providers img {
  width: 24px;
  height: 24px;
  display: inline-block;
  margin: 0;
  margin-right: 1rem;
}

table.supported-providers div a {
  text-decoration: none;
  border-bottom: none;
  font-weight: normal;
}

table.supported-providers div a:hover {
  text-decoration: underline;
}


import { bundle } from '@apidevtools/json-schema-ref-parser';
import axios from 'axios';
import { existsSync, mkdirSync, writeFileSync } from 'node:fs';
import { readFile } from 'node:fs/promises';
import path from 'node:path';
import { dash, group } from 'radash';
import { fileURLToPath } from 'url';
import mintConfig from './mint-base.json' assert { type: 'json' };

const BASE_URL = 'https://api.withterminal.com';

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);

function recursiveClean(spec) {
  if (typeof spec !== 'object' || spec === null) {
    return spec;
  }

  if (Array.isArray(spec)) {
    return spec.map(recursiveClean);
  }

  // replace anyOf with oneOf
  if ('anyOf' in spec) {
    // TODO: this is a hack to fix the spec, we should fix the spec in the source
    // we initially weren't able to use oneOf on our end when setting state
    // to null on IFTA reports so we used anyOf. Nirvana asked us to change to
    // use oneOf instead as it was more correct and didn't break their code-gen
    spec.oneOf = spec.anyOf;
    delete spec.anyOf;
  }

  if ('x-stoplight' in spec) {
    delete spec['x-stoplight'];
  }

  if ('x-internal' in spec) {
    delete spec['x-internal'];
  }

  for (const key in spec) {
    recursiveClean(spec[key]);
  }

  return spec;
}

function memo(fn) {
  let lastArg;
  let lastResult;
  return async (arg) => {
    if (arg === lastArg) {
      return lastResult;
    }

    lastArg = arg;
    lastResult = await fn(arg);
    return lastResult;
  };
}

/**
 * Removes expandable objects from the spec and replaces them with their
 * corresponding ID reference. This will make the specs easier for clients to
 * consume and generate code from without having to deal with the expandable objects.
 *
 * TODO: come up with a better way to handle expandable objects in the spec
 * would ideally want to use expand but we weren't able to get it to work with
 * ajv validation. It would also require a larger refactor to the codebase to
 * ensure we have a consistent way to handle expandable objects.
 */
function removeExpandable(spec) {
  if (typeof spec !== 'object' || spec === null) {
    return spec;
  }

  if (Array.isArray(spec)) {
    return spec.map(removeExpandable);
  }

  if ('$ref' in spec && isString(spec.$ref)) {
    const resource = spec.$ref.match(/#\/components\/schemas\/Expandable(.+)/);

    if (resource) {
      spec.$ref = `#/components/schemas/${resource[1]}Id`;
    }

    return spec;
  }

  for (const key in spec) {
    removeExpandable(spec[key]);
  }

  return spec;
}

async function readSpec() {
  const spec = await readFile(
    path.join(__dirname, '../specs/telematics.openapi.json'),
    'utf8'
  );

  return await bundle(
    JSON.parse(spec.replace(/"\$ref": "\.\//g, `"$ref": "../specs/`))
  );
}

const getSpec = memo(async ({ includeExpandable }) => {
  let spec = await readSpec();
  spec = recursiveClean(spec);
  if (!includeExpandable) {
    spec = removeExpandable(spec);
  }
  return spec;
});

const buildOperationContent = (operation) => {
  const [shortDescription, ...restDescription] = (
    operation.description ?? ''
  ).split('\n');

  const content = `---
title: "${operation.summary}"
${shortDescription ? `description: "${shortDescription}"` : ''}
openapi: "${operation.method.toUpperCase()} ${operation.path}"
---
${restDescription.join('\n').trim()}`;

  return content;
};

const buildSchemaContent = (schemaName, schema) => {
  const [shortDescription, ...restDescription] = (
    schema.description ?? ''
  ).split('\n');

  const content = `---
title: "${schema.title}"
${shortDescription ? `description: "${shortDescription}"` : ''}
openapi-schema: "${schemaName}"
---
${restDescription.join('\n').trim()}`;

  return content;
};

function cleanUpFilepath(filepath) {
  return filepath.replace('./', '').replace('.mdx', '');
}

function writeOperationDocs(operation) {
  const result = [];

  for (const tag of operation.tags ?? []) {
    const tagDir = `./api-reference/${dash(tag)}`;

    if (!existsSync(tagDir)) {
      mkdirSync(tagDir);
    }

    const filename = `${dash(operation.operationId)}.mdx`;
    const filepath = path.join(tagDir, filename);

    const isHiddenOperation =
      operation.hasOwnProperty('x-hidden') && operation['x-hidden'];

    writeFileSync(filepath, buildOperationContent(operation));

    result.push({
      tag,
      operationId: operation.operationId,
      filepath: cleanUpFilepath(filepath),
      isHiddenOperation
    });
  }

  return result;
}

function writeWebhookSchemaDocs(schemaName, schema) {
  const tagDir = `./api-reference/webhook-events`;

  if (!existsSync(tagDir)) {
    mkdirSync(tagDir);
  }

  const filename = `${dash(schemaName)}.mdx`;
  const filepath = path.join(tagDir, filename);

  writeFileSync(filepath, buildSchemaContent(schemaName, schema));

  return cleanUpFilepath(filepath);
}

async function generateReference() {
  const spec = await getSpec({ includeExpandable: true });

  if (!existsSync('./api-reference')) {
    mkdirSync('./api-reference');
  }

  writeFileSync('./terminal.openapi.json', JSON.stringify(spec, null, 2));

  const operations = Object.entries(spec.paths).flatMap(([path, methods]) =>
    Object.entries(methods).map(([method, operation]) => ({
      ...operation,
      path,
      method
    }))
  );

  const outputPages = operations.flatMap((operation) =>
    writeOperationDocs(operation)
  );

  const pagesByTag = group(outputPages, (op) => op.tag);

  const webhookEvents = Object.entries(spec.components.schemas)
    .filter(([_, schema]) => {
      if (!schema['x-tags'] || !Array.isArray(schema['x-tags'])) {
        return false;
      }

      return schema['x-tags'].includes('Webhook Events');
    })
    .map(([schemaName, schema]) => ({
      schemaName,
      type: schema.title,
      schema,
      filepath: writeWebhookSchemaDocs(schemaName, schema)
    }));

  const webhookOverviewPageFilepath =
    './api-reference/webhook-events/overview.mdx';

  const webhookOverviewPageContent = `---
title: "Event Types"
description: "Terminal sends webhook events to your server to notify you of events that happen in your Terminal account."
---
${webhookEvents
  .map(({ type, filepath }) => `- [${type}](/${filepath})`)
  .join('\n')}
`;

  writeFileSync(webhookOverviewPageFilepath, webhookOverviewPageContent);

  const apiReferenceNavItems = Object.entries(pagesByTag)
    .map(([tag, operations]) => ({
      group: tag,
      pages: operations
        .filter((op) => !op.isHiddenOperation)
        .map(({ filepath }) => filepath)
    }))
    .filter(({ pages }) => pages.length > 0);

  const outputConfig = {
    ...mintConfig,
    navigation: mintConfig.navigation.concat(apiReferenceNavItems).concat([
      {
        group: 'Webhook Events',
        pages: [
          cleanUpFilepath(webhookOverviewPageFilepath),
          ...webhookEvents.map(({ filepath }) => filepath)
        ]
      }
    ])
  };

  writeFileSync('mint.json', JSON.stringify(outputConfig));

  console.log('API Reference generated!');
}

function pascalToCapitalCase(str) {
  // add a space before all caps unless it's an acronym
  return str.replace(/([A-Z][a-z])/g, ' $1').trim();
}

function statusIcon(status) {
  switch (status) {
    case 'supported':
      return '🟢';
    case 'not_supported_by_terminal':
      return '🌕';
    case 'not_supported_by_provider':
      return '🔴';

    default:
      throw new Error(`Unknown status: ${status}`);
  }
}

function formatTable(
  rows,
  options = {
    centerData: false
  }
) {
  const columns = Array.from(new Set(rows.flatMap((row) => Object.keys(row))));

  const table = `
<table className="supported-providers"><thead><tr>${columns
    .map(
      (heading, index) =>
        `<th className="${
          index > 0 && options.centerData ? 'center-text' : ''
        }">${heading}</th>`
    )
    .join('')}</tr></thead><tbody>${rows
    .map(
      (row) =>
        `<tr>${columns
          .map(
            (cell, index) =>
              `<td className="${
                index > 0 && options.centerData ? 'center-text' : ''
              }">${row[cell] ?? '-'}</td>`
          )
          .join('')}</tr>`
    )
    .join('')}</tbody></table>
  `.trim();

  return table;
}

function buildSupportedModelsTable(data) {
  const rows = data.map((row) => {
    const { name, icon, supportedModels } = row;

    const support = Object.entries(supportedModels).reduce(
      (acc, [model, modelSupport]) => {
        return {
          ...acc,
          [pascalToCapitalCase(model)]: statusIcon(
            modelSupport.supportedOperations.read
          ),
          ...(model === 'VehicleLocation' && {
            'Historical Locations': modelSupport.availableHistory ? '🟢' : '🔴'
          })
        };
      },
      {}
    );

    return {
      Provider: `<div><img src="${icon}" alt="${name}" /><span>${name}</span></div>`,
      ...support
    };
  });

  return formatTable(rows, { centerData: true });
}

function buildAvailableHistoryTable(data) {
  const rows = data.map((row) => {
    const { name, icon, supportedModels } = row;
    return {
      Provider: `<div><img src="${icon}" alt="${name}" /><span>${name}</span></div>`,
      'Available History':
        supportedModels.VehicleLocation.availableHistory ?? '*Not Supported*'
    };
  });

  return formatTable(rows);
}

function buildSafetyEventsTable(data) {
  const rows = data.map((row) => {
    const { name, icon, supportedModels } = row;
    return {
      Provider: `<div><img src="${icon}" alt="${name}" /><span>${name}</span></div>`,
      ...supportedModels.SafetyEvent.types.reduce((acc, type) => {
        return {
          ...acc,
          ['`' + type + '`']: '✅'
        };
      }, {})
    };
  });

  return formatTable(rows, { centerData: true });
}

function buildSampleRateTable(data) {
  const rows = data.map((row) => {
    const { name, icon, supportedModels } = row;
    return {
      Provider: `<div><img src="${icon}" alt="${name}" /><span>${name}</span></div>`,
      'Sample Rate': supportedModels.VehicleLocation.sampleRate
    };
  });

  return formatTable(rows);
}

async function generateProviderReference() {
  const allProviders = await axios(`${BASE_URL}/tsp/v1/providers`).then(
    (res) => res.data
  );

  const liveProviders = allProviders.filter((p) => p.status === 'live');

  writeFileSync(
    '_snippets/supported-providers-table.mdx',
    buildSupportedModelsTable(liveProviders)
  );

  writeFileSync(
    '_snippets/supported-history.mdx',
    buildAvailableHistoryTable(liveProviders)
  );

  writeFileSync(
    '_snippets/supported-safety-events.mdx',
    buildSafetyEventsTable(liveProviders)
  );

  writeFileSync(
    '_snippets/supported-sample-rate.mdx',
    buildSampleRateTable(liveProviders)
  );

  console.log('Provider Reference generated!');
}

Promise.all([generateReference(), generateProviderReference()]);


Data Characteristics

Supported Models

Safety Events

API Reference

Supported Providers

Website

Product Roadmap

Terminal

Get Started

This document provides an overview of Terminal's integration with Omnitracs ES. It shows which data models are currently available in production and which ones are in active development.

Omnitracs ES

Overview

Let's introduce you to some key features and concepts of the Terminal API.

How Terminal Works

Here's a step-by-step guide to get started integrating telematics data with Terminal.

Getting Started

Terminal provides a hosted 'Link' that makes it easy to authenticate with any telematics provider. With only a few steps you will be able to provide customers/partners an easy self-serve flow to connect their telematics account.

Link Component

Terminal provides SDKs to make it easy to integrate with your application.

Published SDKs

Syncing Data

Follow this guide to configure an OAuth2 client for Motive integration

Motive OAuth Configuration

Here's a step-by-step guide to configure an OAuth2 client for Samsara

Samsara OAuth Configuration

Test your telematics integrations with Terminal's API

Sandbox Environment

Custom Identifiers

Passthrough

Raw Data

Webhooks

Third Party Extensions

Receive detailed reports when crash events are detected across connections

Crash Reports

Environments

Authentication

Rate Limits

Resource Expansion

Pagination

Serialization

Provider List

This document provides an overview of Terminal's integration with ABC ELD. It shows which data models are currently available in production and which ones are in active development.

ABC ELD

This document provides an overview of Terminal's integration with Action ELD. It shows which data models are currently available in production and which ones are in active development.

Action ELD

This document provides an overview of Terminal's integration with Advantage One. It shows which data models are currently available in production and which ones are in active development.

Advantage One

This document provides an overview of Terminal's integration with AMPM ELD. It shows which data models are currently available in production and which ones are in active development.

AMPM ELD

This document provides an overview of Terminal's integration with Apex Ultima. It shows which data models are currently available in production and which ones are in active development.

Apex Ultima

This document provides an overview of Terminal's integration with Apollo Compass. It shows which data models are currently available in production and which ones are in active development.

Apollo Compass

This document provides an overview of Terminal's integration with Apollo ELD. It shows which data models are currently available in production and which ones are in active development.

Apollo ELD

This document provides an overview of Terminal's integration with Argos Connected Solutions. It shows which data models are currently available in production and which ones are in active development.

Argos Connected Solutions

This document provides an overview of Terminal's integration with Attrix. It shows which data models are currently available in production and which ones are in active development.

Attrix

This document provides an overview of Terminal's integration with Azuga. It shows which data models are currently available in production and which ones are in active development.

Azuga

This document provides an overview of Terminal's integration with BigRoad. It shows which data models are currently available in production and which ones are in active development.

BigRoad

This document provides an overview of Terminal's integration with Black Bear. It shows which data models are currently available in production and which ones are in active development.

Black Bear

This document provides an overview of Terminal's integration with Blue Arrow Telematics. It shows which data models are currently available in production and which ones are in active development.

Blue Arrow Telematics

This document provides an overview of Terminal's integration with Blue Horse ELD. It shows which data models are currently available in production and which ones are in active development.

Blue Horse ELD

This document provides an overview of Terminal's integration with Cobra ELD. It shows which data models are currently available in production and which ones are in active development.

Cobra ELD

This document provides an overview of Terminal's integration with Columbus ELD. It shows which data models are currently available in production and which ones are in active development.

Columbus ELD

This document provides an overview of Terminal's integration with Conti-GO. It shows which data models are currently available in production and which ones are in active development.

Conti-GO

This document provides an overview of Terminal's integration with Daily ELD. It shows which data models are currently available in production and which ones are in active development.

Daily ELD

This document provides an overview of Terminal's integration with DFL ELD. It shows which data models are currently available in production and which ones are in active development.

DFL ELD

This document provides an overview of Terminal's integration with DY ELD. It shows which data models are currently available in production and which ones are in active development.

DY ELD

This document provides an overview of Terminal's integration with Eagle Wireless. It shows which data models are currently available in production and which ones are in active development.

Eagle Wireless

This document provides an overview of Terminal's integration with ELD Books. It shows which data models are currently available in production and which ones are in active development.

ELD Books

This document provides an overview of Terminal's integration with ELD Mandate HOS. It shows which data models are currently available in production and which ones are in active development.

ELD Mandate HOS

This document provides an overview of Terminal's integration with ELD Mandate Plus. It shows which data models are currently available in production and which ones are in active development.

ELD Mandate Plus

This document provides an overview of Terminal's integration with ELD Mandate Prime. It shows which data models are currently available in production and which ones are in active development.

ELD Mandate Prime

This document provides an overview of Terminal's integration with ELD One. It shows which data models are currently available in production and which ones are in active development.

ELD One

This document provides an overview of Terminal's integration with ELD Rider. It shows which data models are currently available in production and which ones are in active development.

ELD Rider

This document provides an overview of Terminal's integration with EnVue Telematics. It shows which data models are currently available in production and which ones are in active development.

EnVue Telematics

This document provides an overview of Terminal's integration with EROAD. It shows which data models are currently available in production and which ones are in active development.

EROAD

This document provides an overview of Terminal's integration with EVA ELD. It shows which data models are currently available in production and which ones are in active development.

EVA ELD

This document provides an overview of Terminal's integration with EVO ELD. It shows which data models are currently available in production and which ones are in active development.

EVO ELD

This document provides an overview of Terminal's integration with Factor ELD. It shows which data models are currently available in production and which ones are in active development.

Factor ELD

This document provides an overview of Terminal's integration with Flash ELogs. It shows which data models are currently available in production and which ones are in active development.

Flash ELogs

This document provides an overview of Terminal's integration with Fleet Complete Hub. It shows which data models are currently available in production and which ones are in active development.

Fleet Complete Hub

This document provides an overview of Terminal's integration with Fleet Profit Center. It shows which data models are currently available in production and which ones are in active development.

Fleet Profit Center

This document provides an overview of Terminal's integration with Fleetistics. It shows which data models are currently available in production and which ones are in active development.

Fleetistics

This document provides an overview of Terminal's integration with FM ELD. It shows which data models are currently available in production and which ones are in active development.

FM ELD

This document provides an overview of Terminal's integration with Fort Knox ELD. It shows which data models are currently available in production and which ones are in active development.

Fort Knox ELD

This document provides an overview of Terminal's integration with Forza ELD. It shows which data models are currently available in production and which ones are in active development.

Forza ELD

This document provides an overview of Terminal's integration with Geotab. It shows which data models are currently available in production and which ones are in active development.

Geotab

This document provides an overview of Terminal's integration with Geotab AT&T. It shows which data models are currently available in production and which ones are in active development.

Geotab AT&T

This document provides an overview of Terminal's integration with GoFleet. It shows which data models are currently available in production and which ones are in active development.

GoFleet

This document provides an overview of Terminal's integration with GoGPS. It shows which data models are currently available in production and which ones are in active development.

GoGPS

This document provides an overview of Terminal's integration with GPS Insight. It shows which data models are currently available in production and which ones are in active development.

GPS Insight

This document provides an overview of Terminal's integration with GPS Tracking Canada. It shows which data models are currently available in production and which ones are in active development.

GPS Tracking Canada

This document provides an overview of Terminal's integration with GPSTab. It shows which data models are currently available in production and which ones are in active development.

GPSTab

This document provides an overview of Terminal's integration with GrayBox Solutions. It shows which data models are currently available in production and which ones are in active development.

GrayBox Solutions

This document provides an overview of Terminal's integration with Gridline. It shows which data models are currently available in production and which ones are in active development.

Gridline

This document provides an overview of Terminal's integration with Hero ELD. It shows which data models are currently available in production and which ones are in active development.

Hero ELD

This document provides an overview of Terminal's integration with High Point GPS. It shows which data models are currently available in production and which ones are in active development.

High Point GPS

This document provides an overview of Terminal's integration with HOS Reporter Plus. It shows which data models are currently available in production and which ones are in active development.

HOS Reporter Plus

This document provides an overview of Terminal's integration with HOS247. It shows which data models are currently available in production and which ones are in active development.

HOS247

This document provides an overview of Terminal's integration with ID ELD. It shows which data models are currently available in production and which ones are in active development.

ID ELD

This document provides an overview of Terminal's integration with Infinity ELD. It shows which data models are currently available in production and which ones are in active development.

Infinity ELD

This document provides an overview of Terminal's integration with IntelliShift. It shows which data models are currently available in production and which ones are in active development.

IntelliShift

This document provides an overview of Terminal's integration with IoTab. It shows which data models are currently available in production and which ones are in active development.

IoTab

This document provides an overview of Terminal's integration with ISAAC Instruments. It shows which data models are currently available in production and which ones are in active development.

ISAAC Instruments

This document provides an overview of Terminal's integration with Just ELD. It shows which data models are currently available in production and which ones are in active development.

Just ELD

This document provides an overview of Terminal's integration with KSK ELD. It shows which data models are currently available in production and which ones are in active development.

KSK ELD

This document provides an overview of Terminal's integration with Linxup. It shows which data models are currently available in production and which ones are in active development.

Linxup

This document provides an overview of Terminal's integration with MasterELD. It shows which data models are currently available in production and which ones are in active development.

MasterELD

This document provides an overview of Terminal's integration with Monarch Tracking. It shows which data models are currently available in production and which ones are in active development.

Monarch Tracking

This document provides an overview of Terminal's integration with Moonlight ELD. It shows which data models are currently available in production and which ones are in active development.

Moonlight ELD

This document provides an overview of Terminal's integration with Motion ELD. It shows which data models are currently available in production and which ones are in active development.

Motion ELD

This document provides an overview of Terminal's integration with Motive. It shows which data models are currently available in production and which ones are in active development.

Motive

This document provides an overview of Terminal's integration with Mountain ELD. It shows which data models are currently available in production and which ones are in active development.

Mountain ELD

This document provides an overview of Terminal's integration with Omnitracs XRS. It shows which data models are currently available in production and which ones are in active development.

Omnitracs XRS

This document provides an overview of Terminal's integration with OneStep GPS. It shows which data models are currently available in production and which ones are in active development.

OneStep GPS

This document provides an overview of Terminal's integration with Ontime ELD. It shows which data models are currently available in production and which ones are in active development.

Ontime ELD

This document provides an overview of Terminal's integration with Optima ELD. It shows which data models are currently available in production and which ones are in active development.

Optima ELD

This document provides an overview of Terminal's integration with Phoenix ELD. It shows which data models are currently available in production and which ones are in active development.

Phoenix ELD

This document provides an overview of Terminal's integration with Pro Ride ELD. It shows which data models are currently available in production and which ones are in active development.

Pro Ride ELD

This document provides an overview of Terminal's integration with PTI ELD. It shows which data models are currently available in production and which ones are in active development.

PTI ELD

This document provides an overview of Terminal's integration with Radical ELD. It shows which data models are currently available in production and which ones are in active development.

Radical ELD

This document provides an overview of Terminal's integration with RealELD. It shows which data models are currently available in production and which ones are in active development.

RealELD

This document provides an overview of Terminal's integration with Reliable ELD. It shows which data models are currently available in production and which ones are in active development.

Reliable ELD

This document provides an overview of Terminal's integration with Renaissance ELD. It shows which data models are currently available in production and which ones are in active development.

Renaissance ELD

This document provides an overview of Terminal's integration with RoadStar. It shows which data models are currently available in production and which ones are in active development.

RoadStar

This document provides an overview of Terminal's integration with Robinhood ELD. It shows which data models are currently available in production and which ones are in active development.

Supported Providers

Provider Details

Omnitracs ES

Data Characteristics

Supported Models

Vehicle

Driver

Vehicle Location

Vehicle Stat Log

IFTA Summary

HOS Log

HOS Available Time

HOS Daily Log

Group

Device

Trip

Safety Event

Camera Media

Trailer

Trailer Location

Safety Events

Supported Providers

Provider Details

​Data Characteristics

​Supported Models

Vehicle

Driver

Vehicle Location

Vehicle Stat Log

IFTA Summary

HOS Log

HOS Available Time

HOS Daily Log

Group

Device

Trip

Safety Event

Camera Media

Trailer

Trailer Location

​Safety Events

Data Characteristics

Supported Models

Safety Events