Products/Operations
stateful6 platforms4 source families
Understand every moving asset

InTouch Telematics

Live tracking, trips, devices, vehicles, events, geofences, and fleet intelligence.

Start building Get credentials

Connect vehicles, phones, and IoT devices to a longitudinal operational model. InTouch combines ingestion, identity, asset assignment, trip construction, event detection, live state, historical playback, and reporting. Integrations should model provisioning and lifecycle transitions explicitly.

Capabilities

Device and vehicle provisioningProduction guidance, platform support, examples, and operational considerations included.01
Live location and historical trailsProduction guidance, platform support, examples, and operational considerations included.02
Trips, stoppages, and eventsProduction guidance, platform support, examples, and operational considerations included.03
Geofences, alerts, and notificationsProduction guidance, platform support, examples, and operational considerations included.04
Driver behavior and fleet reportsProduction guidance, platform support, examples, and operational considerations included.05
Mobile sensor-based tracking SDKsProduction guidance, platform support, examples, and operational considerations included.06

Available platforms

Keep business identifiers and server-side policy portable; use the native surface where device integration or long-lived state matters.

OAuth bearer with project and asset entitlement

Generate a time-bound InTouch bearer token from the subscribed project's client credentials. Separate provisioning identities from data-plane tracking tokens and rotate device credentials independently.

  • Use separate projects for development, staging, and production.
  • Apply the narrowest domain, IP, platform, product, and resource scopes available.
  • Never ship a server secret in a browser bundle, mobile binary, prompt, or public repository.

Quickstart

Replace placeholders with credentials from the developer console. Examples include the lifecycle and failure-handling context that short snippets usually omit.

InTouch Telematics quickstart
type AssetEvent = {
  id: string;
  assetId: string;
  occurredAt: string;
  type: "position" | "ignition" | "geofence.entered" | "geofence.exited";
  position?: { latitude: number; longitude: number; speedKph?: number };
};

export async function handleAssetEvent(event: AssetEvent) {
  // Idempotency matters: delivery may be retried.
  if (await events.exists(event.id)) return;
  await events.transaction(async () => {
    await events.record(event);
    await assets.apply(event.assetId, event);
  });
}
Before productionRestrict and rotate credentialsHandle timeouts and typed errorsAdd tracing without logging secretsTest quota and degraded-mode behavior

Vehicle from activation to daily operations

The complete fleet journey spans control-plane and data-plane state.

1
State · provisioned

Provision

Create the organization, project, asset, device, and entitlements.

asset.created
2
State · active

Activate

Securely bind the physical device or mobile SDK to the asset.

device.activated
3
State · online

Ingest

Accept ordered and delayed telemetry while tracking connection health.

position.received
4
State · in_trip

Operate

Build trips, evaluate geofences, notify operators, and power live views.

trip.started
5
State · maintenance

Maintain

Diagnose gaps, replace devices, transfer assets, and preserve history.

device.replaced
6
State · retired

Retire

Revoke credentials and detach hardware without deleting audit history.

asset.retired

Operate the complete lifecycle

These blueprints name every state, actor, command, event, invariant, durable record, retry boundary, failure recovery, source contract, and operational signal.

Browse all stateful journey blueprints

Source repositories

Reference content is reconciled against these public and private source families. Version, authentication generation, and maturity are recorded before content is promoted.

Browse all 53 related integration guides