Ellipse Gradient for Header

Samsara Integration Guide

Connect Samsara fleet, telematics, safety, route, sensor, and asset data with enterprise systems through REST APIs, selected webhooks, and Martini workflows.

Samsara integration options at a glance

Samsara’s primary integration surface is its versioned REST API, which exposes fleet, vehicle, driver, asset, safety, route, sensor, maintenance, and operational data. Samsara also supports API tokens and OAuth 2.0, while webhooks provide notifications for selected event and data scenarios rather than universal change capture. Resource-specific endpoints support pagination, time ranges, filters, and larger data retrievals. Martini can consume these APIs, receive Samsara webhook notifications, retrieve authoritative resources, apply mappings and business rules, and synchronize normalized data with applications, databases, and reporting platforms through scheduled or event-driven workflows.

Integration pointSupported by Samsara?Common use casesHow Martini supports it
REST APIsYesAccess Vehicles, Drivers, Assets, Sensors, Routes, Safety Events, maintenance, telematics, and other operational data through Samsara’s versioned API.Martini can consume Samsara REST endpoints from workflows, transform responses, apply business rules, and expose normalized APIs or write to downstream systems.
Webhooks and outbound callbacksLimitedReceive notifications for selected Samsara events and data scenarios. Coverage does not extend universally to every object or field change.Martini can expose a receiving API or webhook-triggered workflow, validate the request, deduplicate the event, retrieve the current Samsara resource, and continue processing.
Bulk, asynchronous, and batch retrievalLimitedRetrieve larger vehicle-statistics and operational datasets using resource-specific endpoints, time ranges, filters, multiple identifiers, and pagination.Martini can implement scheduled workflows with bounded windows, cursor checkpoints, controlled concurrency, resumable processing, and rate-limit handling.
AuthenticationYesAuthenticate with administrator-managed API tokens or OAuth 2.0 for user-authorized and multi-organization applications, subject to permissions and scopes.Martini can store tokens, OAuth client secrets, refresh credentials, and webhook secrets in environment-specific secrets management and apply them to API requests.
File and attachment APIsLimitedAccess media and operational files associated with selected resources, including some safety-related media or documents. Coverage is resource-specific.Martini can call the relevant Samsara endpoint, retain required metadata or content, and apply retention and security rules without assuming universal attachment support.
Scheduled synchronizationYesPoll objects without suitable webhook coverage and perform incremental or historical retrieval using timestamps, cursors, filters, or bounded time ranges.Martini scheduler-triggered workflows can retrieve pages, persist checkpoints, normalize data, and retry incomplete work.
Database accessNot confirmedNo direct customer SQL database or general-purpose database interface was confirmed for Samsara data.Martini can persist API results in supported databases, but it should obtain source data through Samsara APIs and supported exports rather than direct Samsara database access.

How Samsara exposes data and business events

Samsara REST APIs

Samsara’s versioned REST API is the main integration surface for fleet, telematics, safety, driver, asset, route, sensor, maintenance, and operational data. Resource-specific endpoints determine available filters, writes, pagination, and time-range behavior.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with an API token or OAuth credential, calls the relevant endpoint, follows pagination or continuation values, maps the response into a canonical model, applies business rules, and writes the result to a target system or database.

Implementation sequence

Authenticate the request with a secured Samsara credential
Call the resource-specific Samsara REST endpoint
Follow the returned cursor or continuation value
Map the response into the canonical integration model
Apply validation and business rules
Write the result and store the synchronization checkpoint

Samsara Webhooks

Samsara supports webhook-style notifications for selected event and data scenarios. Notifications should not be treated as universal change-data-capture events, and payload completeness varies by scenario.

Martini implementation pattern

Martini implementation pattern: expose a receiving API or webhook-triggered workflow, validate the incoming request and available verification data, detect duplicate delivery, retrieve the current Samsara object, and then process the authoritative response.

Implementation sequence

Receive the Samsara webhook notification
Validate the request and available verification information
Check the event identifier or derived idempotency key
Retrieve the current Samsara resource through the REST API
Map the authoritative resource to the target model
Record processing status and route failures for retry

Scheduled Samsara synchronization

Scheduled retrieval is appropriate for objects without suitable webhook coverage and for historical or high-volume data. Samsara endpoints may use timestamps, cursors, filters, or bounded time ranges.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow for each resource and time window, retrieves pages under controlled concurrency, persists progress after successful batches, and resumes from the last durable checkpoint after transient failure.

Implementation sequence

Start the workflow on a defined schedule
Load the last resource and time checkpoint
Retrieve a bounded Samsara page or time window
Process and persist the normalized results
Apply rate-limit backoff when required
Store the next cursor or checkpoint

Samsara batch and telemetry retrieval

Samsara provides resource-specific methods for larger operational and telemetry datasets, including vehicle statistics. This is not a universal bulk import interface, so endpoint behavior must be evaluated per resource.

Martini implementation pattern

Martini implementation pattern: split historical or high-volume extraction into bounded windows and pages, use resumable checkpoints, normalize timestamps and measurements, and persist results outside a single workflow payload.

Implementation sequence

Define the resource, identifiers, and bounded time window
Request the Samsara dataset or telemetry page
Normalize measurements, timestamps, and identifiers
Persist the batch and its processing checkpoint
Continue until the endpoint indicates completion
Route failed batches for controlled retry

Common Samsara integration patterns

Pattern 1: Synchronize Samsara fleet data to an operational database

When to use this pattern

Use this pattern when Vehicles, Drivers, Assets, and related operational data must be available to reporting, logistics, or enterprise applications. Scheduled retrieval is suitable when webhook coverage is unavailable or when a complete, checkpointed dataset is required.

Integration direction
Samsara
Martini
SQL database
Example Mapping
Samsara FieldCanonical FieldTarget Field
vehicle.idasset.externalIdvehicle_external_id
vehicle.nameasset.displayNamevehicle_name
driver.idoperator.externalIddriver_external_id
updatedAtsourceUpdatedAtsource_updated_at
Martini implementation pattern

A scheduled Martini workflow retrieves each resource independently, follows Samsara pagination, normalizes timestamps to UTC, applies organization and status rules, and upserts rows using stable Samsara identifiers. It stores cursors and checkpoints so a failed page can be retried without replaying the full synchronization.

Martini capabilities used
  • workflows
  • scheduled triggers
  • API consumption
  • pagination handling
  • data mapping
  • SQL database access
  • checkpointing
  • error handling

Pattern 2: Route Samsara safety events to ServiceNow

When to use this pattern

Use this pattern when Safety Events such as collisions, harsh driving, speeding, or distracted driving should create operational incidents or review tasks. Selected Samsara notifications can reduce latency, while polling covers unsupported scenarios.

Integration direction
Samsara
Martini
ServiceNow
Example Mapping
Samsara FieldCanonical FieldTarget Field
safetyEvent.idevent.externalIdcorrelation_id
safetyEvent.typeevent.categorycategory
safetyEvent.severityevent.prioritypriority
vehicle.idasset.externalIdconfiguration_item
Martini implementation pattern

Martini receives a supported Samsara notification, validates and deduplicates it, retrieves the complete Safety Event, applies severity and asset-routing rules, and creates or updates the ServiceNow case. Transient Samsara or ServiceNow failures are retried, while permanent mapping errors are routed for review.

Martini capabilities used
  • API exposure
  • webhook consumption
  • REST API consumption
  • idempotency rules
  • data mapping
  • business rules
  • error handling
  • retry orchestration

Pattern 3: Synchronize Samsara routes with transportation operations

When to use this pattern

Use this pattern when route plans, stops, progress, and execution status need to be aligned with Oracle Transportation Management, NetSuite, or another logistics application. The exact reverse-write flow depends on documented write operations for each Samsara resource.

Integration direction
Samsara
Martini
Oracle Transportation Management
Example Mapping
Samsara FieldCanonical FieldTarget Field
route.idshipment.externalRouteIdroute_id
route.stopsshipment.stopsstop_sequence
route.progressshipment.executionStatusexecution_status
route.updatedAtshipment.lastSamsaraUpdatesource_updated_at
Martini implementation pattern

A Martini workflow retrieves Routes and stops incrementally, maps Samsara progress and time values to the transportation model, enriches records with shipment context, and submits only material changes. It handles pagination, rate limits, missing routes, and target acknowledgements before advancing the checkpoint.

Martini capabilities used
  • scheduled workflows
  • REST API consumption
  • data transformation
  • business rules
  • incremental synchronization
  • rate-limit handling
  • checkpointing

Pattern 4: Monitor Samsara sensors and cold-chain exceptions

When to use this pattern

Use this pattern when Sensor readings, temperature information, alerts, and asset context must generate operational exceptions or reporting data. Notifications may be used for supported event types, with scheduled retrieval as a fallback.

Integration direction
Samsara
Martini
ServiceNow
Example Mapping
Samsara FieldCanonical FieldTarget Field
sensor.idsensor.externalIdsensor_id
reading.temperaturemeasurement.valuetemperature
reading.timestampmeasurement.observedAtobserved_at
asset.idasset.externalIdconfiguration_item
Martini implementation pattern

Martini retrieves sensor data in bounded windows, normalizes units and timestamps, evaluates threshold and asset-context rules, and creates or updates ServiceNow work items for exceptions. Duplicate notifications are suppressed with a stable event or measurement key, and transient failures are retried.

Martini capabilities used
  • scheduled triggers
  • webhook consumption
  • API consumption
  • data mapping
  • threshold rules
  • idempotency
  • error handling

Applications commonly integrated with Samsara

Samsara data can be connected to enterprise applications for customer operations, maintenance, logistics, workforce processes, and reporting. These relationships describe practical Martini integration targets and do not imply that Samsara provides native integrations with the listed products.

Application Scenario Direction Martini Pattern
Salesforce Synchronize Vehicles, Drivers, delivery information, Safety Events, and service activity with account, field-service, or customer operations. Samsara → Martini → Salesforce Use scheduled REST retrievals and selected webhook notifications to obtain current Samsara resources, normalize them in Martini, apply account or severity rules, and upsert Salesforce objects using stable Samsara identifiers.
ServiceNow Create incidents, maintenance cases, or operational tasks from Samsara Safety Events, vehicle issues, and sensor alerts. Samsara → Martini → ServiceNow Receive a supported Samsara notification or poll relevant resources, retrieve the complete object, map severity and asset context, prevent duplicate cases with an idempotency key, and create or update ServiceNow records.
NetSuite Align fleet assets, delivery status, route information, and operational events with orders, fulfillment, and financial processes. Samsara → Martini → NetSuite Run scheduled Samsara API workflows, map Routes, Vehicles, and delivery context to NetSuite records, apply endpoint-specific write rules, and route failed updates for retry or review.
SAP S/4HANA Combine fleet and transportation telemetry with logistics, maintenance, procurement, and asset processes. Samsara → Martini → SAP S/4HANA Retrieve Samsara operational data, transform it into SAP-compatible structures, apply privacy and organizational rules, and submit validated messages or API requests with checkpointed retries.
Microsoft Dynamics 365 Use vehicle, driver, route, and asset data in field service, sales, customer service, or supply-chain workflows. Samsara → Martini → Microsoft Dynamics 365 Orchestrate Samsara REST calls and selected notifications in Martini, map operational identifiers to Dynamics 365 entities, and use business rules to control updates and duplicate handling.
Oracle Transportation Management Correlate Samsara vehicle location and route execution data with transportation planning and shipment execution. Samsara → Martini → Oracle Transportation Management Retrieve Routes, locations, and execution data in bounded windows, transform Samsara timestamps and identifiers, enrich shipment context, and submit updates with rate-limit-aware retries.
Workday Support approved driver or workforce-related processes where Samsara operational data must be associated with personnel records. Samsara → Martini → Workday Use a least-privilege Samsara credential, match approved Driver data to Workday identities, mask sensitive fields, and process only the workforce attributes required by the business workflow.
Power BI Load fleet, route, safety, and sensor data into reporting models and operational dashboards. Samsara → Martini → Power BI Extract Samsara data through scheduled, paginated workflows, normalize it and persist it in a reporting database or data pipeline, then expose stable datasets for Power BI consumption.

How to build a Samsara integration in Martini

Objective

Establish access to Samsara using the credential model appropriate to the integration, while keeping secrets and environment-specific settings outside workflow logic.

Instructions in Martini

  • Choose an administrator-managed API token or OAuth 2.0 based on the organization and tenancy model
  • Request only the Samsara permissions or OAuth scopes required by the workflow
  • Store tokens, OAuth secrets, refresh credentials, and webhook verification secrets in Martini secrets management
  • Configure the target application credentials and environment variables

Objective

Select an event-driven or scheduled entry point according to Samsara’s coverage for the required object and event.

Instructions in Martini

  • Use a Martini API or webhook-receiving workflow for supported Samsara notifications
  • Use a scheduler for polling, historical retrieval, and objects without appropriate webhook coverage
  • Define resource-specific time windows, cursors, or checkpoints
  • Separate high-volume resources into independently resumable workflows

Objective

Obtain the authoritative Samsara resource and account for pagination, continuation values, and incomplete notification payloads.

Instructions in Martini

  • Receive and validate the notification when using webhooks
  • Retrieve the current Vehicle, Driver, Asset, Sensor, Route, Safety Event, or other resource through REST
  • Follow Samsara cursor or continuation values until the page is complete
  • Use bounded time ranges and filters for telemetry and historical datasets

Objective

Coordinate the Samsara request, enrichment, target calls, checkpointing, and failure paths as a maintainable Martini workflow.

Instructions in Martini

  • Separate resource retrieval from downstream writes where practical
  • Apply controlled concurrency to avoid excessive Samsara request volume
  • Persist progress after successful pages or batches
  • Use reusable workflow logic for authentication, pagination, and response handling

Objective

Convert Samsara’s resource-specific response structures into canonical models and target-specific payloads.

Instructions in Martini

  • Map Samsara identifiers to stable canonical external IDs
  • Normalize timestamps to UTC while preserving relevant local timezone context
  • Transform units, status values, route stops, and event severity as required
  • Validate required fields and tolerate unknown optional fields where safe

Objective

Make operational decisions consistently before writing to downstream systems.

Instructions in Martini

  • Apply severity, threshold, asset-routing, and organizational rules
  • Use event IDs or object ID and timestamp combinations as idempotency keys
  • Mask or exclude sensitive driver and location data when the target does not require it
  • Distinguish writable Samsara resources from read-only synchronization objects

Common Samsara data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
VehiclesSynchronize fleet master data, availability, location context, telemetry, and vehicle identifiers.SQL databases, Salesforce, SAP S/4HANA, Microsoft Dynamics 365, Power BIMartini retrieves Vehicles through REST endpoints, follows pagination, normalizes identifiers and timestamps, and writes checkpointed updates to downstream systems.
DriversSupport driver assignments, safety workflows, hours-of-service context, and approved workforce processes.Salesforce, Workday, SAP S/4HANA, safety applicationsMartini applies least-privilege access, maps driver identifiers to canonical identities, masks sensitive fields where required, and prevents duplicate updates.
AssetsTrack trailers, containers, equipment, and other non-vehicle operational assets.NetSuite, SAP S/4HANA, ServiceNow, SQL databasesMartini retrieves and maps asset status and ownership context, applies business rules, and correlates assets with vehicles, routes, or maintenance processes.
SensorsProcess temperature, door, cargo, environmental, and equipment telemetry or alerts.ServiceNow, Salesforce, Power BI, cold-chain databasesMartini retrieves readings in bounded time windows, normalizes units and timestamps, applies threshold rules, and routes exceptions to operational workflows.
RoutesSynchronize planned or active delivery and service routes, stops, progress, and execution context.Oracle Transportation Management, NetSuite, Microsoft Dynamics 365, customer-notification systemsMartini maps route and stop identifiers, converts time zones to UTC internally, enriches target records, and processes updates incrementally.
Safety EventsCreate safety cases and notifications for harsh driving, collisions, speeding, distracted driving, and related events.ServiceNow, Salesforce, HR or safety applications, Power BIMartini receives selected notifications or polls event endpoints, retrieves the authoritative event, applies severity rules, and uses event identifiers for idempotent processing.

Authentication and security considerations

Authentication options

Samsara supports administrator-managed API tokens and OAuth 2.0. OAuth is generally suited to user-authorized or multi-organization applications, while API tokens can support applicable organization-level integrations.

Least privilege and secret handling

Use the narrowest Samsara permissions or OAuth scopes required by each workflow. Store API tokens, OAuth client secrets, refresh credentials, and webhook verification secrets in Martini environment-specific secrets management rather than embedding them in workflows.

Protected operational data

Driver identity, location, safety, and behavior data may be sensitive. Define access, masking, retention, and audit rules before copying Samsara data into enterprise applications or analytics platforms.

Operational considerations for Samsara integrations

Rate limits and retries

Handle HTTP 429 responses with exponential backoff and jitter, and control concurrency when several workflows share a Samsara organization. Retry transient availability failures while routing authentication, validation, missing-resource, and permanent mapping errors for review.

Pagination and checkpoints

Follow Samsara cursors or continuation values instead of using fixed page counts. Persist checkpoints after successful pages or time windows so large synchronizations can resume safely.

Idempotency and webhook replay

Use a Samsara event identifier, resource identifier, or resource-and-timestamp combination to prevent duplicate downstream updates. Treat webhook requests as untrusted until validated and retrieve the current resource before important decisions.

Time and schema management

Normalize timestamps to UTC while preserving relevant local timezone context. Isolate Samsara-specific mappings, monitor version and deprecation changes, and tolerate unknown optional fields where appropriate.

Testing and observability

Test representative resource types, empty pages, rate limits, deleted resources, duplicate notifications, permission failures, and target-system errors. Monitor workflow logs, checkpoints, retry queues, and synchronization latency.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond point-to-point calls

Martini coordinates Samsara API requests, selected webhook notifications, pagination, enrichment, business rules, downstream writes, checkpoints, and failure handling in reusable workflows rather than distributing logic across isolated scripts.

Controlled data transformation

Martini maps resource-specific Samsara responses into canonical and target-specific models, normalizes timestamps and measurements, validates fields, and applies operational or privacy rules before data is shared.

Reliable operations

Scheduled and event-driven workflows can combine notification-driven processing with authoritative resource retrieval, rate-limit-aware retries, idempotency checks, and resumable synchronization for high-volume telemetry.

Reusable enterprise APIs

Martini can expose a normalized API façade so downstream applications do not each need to understand Samsara authentication, resource structures, pagination, or version-specific mappings.

Frequently asked questions

How can Samsara be integrated with enterprise systems?

Samsara can be integrated through its versioned REST APIs, API tokens or OAuth 2.0, selected webhook notifications, and resource-specific pagination, filters, time ranges, and retrieval endpoints. Scheduled Martini workflows can synchronize Vehicles, Drivers, Assets, Routes, Sensors, Safety Events, and other supported objects with applications, databases, and reporting platforms.

Can Martini integrate with Samsara?

Yes. Martini can integrate with Samsara by consuming its REST APIs and receiving supported Samsara webhook notifications. Martini workflows can retrieve authoritative resources, apply mappings and business rules, synchronize data, and expose normalized APIs for downstream applications.

Do I need a connector to integrate Samsara with Martini?

No. A dedicated Samsara connector is not required. Martini can use Samsara’s confirmed native integration mechanisms, including REST APIs, API tokens, OAuth 2.0, selected webhook notifications, pagination, and resource-specific data retrieval.

Is there any extra Lonti cost to integrate Samsara with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Samsara with Martini. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Samsara, cloud infrastructure, or other third-party systems based on subscriptions, usage, and deployment model.

Which Samsara integration methods should an implementation use?

The Samsara REST API is the primary method for current integrations. Use API tokens for applicable organization-level access and OAuth 2.0 when user authorization or multi-organization access is required. Use selected webhooks for supported notifications, supplemented by scheduled REST retrieval for complete synchronization.

Are Samsara webhooks available for event-driven integrations?

Samsara supports webhooks for selected event and data-notification scenarios, but coverage is not universal across objects or field changes. Martini can receive a notification, validate and deduplicate it, retrieve the current Samsara resource, and then process the authoritative data.

How should Samsara data synchronization handle pagination and large telemetry volumes?

Synchronization should process resource-specific endpoints independently, follow returned cursors or continuation values, and use bounded time windows, filters, and durable checkpoints. Martini scheduled workflows can apply controlled concurrency, retry rate-limited requests, and resume incomplete batches without requesting all historical data repeatedly.

Can Martini expose an API façade for Samsara data?

Yes. Martini can expose a controlled REST API that presents normalized Samsara data to downstream applications. The façade can centralize authentication, filtering, field mappings, business rules, privacy controls, and access to the underlying Samsara REST workflows.

Related Martini documentation

Samsara APIs

Workflows

Data mapping

Security

Operations

Connect Samsara with your enterprise systems

Use Martini to build secure, maintainable Samsara integrations for fleet synchronization, safety automation, route operations, sensor monitoring, and enterprise reporting.

EXPLORE MARTINI
BOOK A DEMO