OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Vehicle master records return JSON under Read Vehicles.
Samsara list vehicle records ↗
List all vehicles · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
after/endCursor traversal supports up to 512 vehicles per page.
Samsara list vehicle records ↗
limit; after · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
updatedAfterTime and createdAfterTime filter the collection.
Samsara list vehicle records ↗
Query Params · Checked 2026-10-16
Access cost barrier -
-
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
Samsara list vehicle records ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
The integration guide explicitly allows privately distributed customer-token integrations.
Samsara application distribution and review requirements ↗
Authentication/distribution options; Manual Tokens · Checked 2026-10-16
Downstream permission -
-
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Samsara list vehicle records ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Address creation and the separately reviewed update operation require Write Addresses.
Samsara create address ↗
Create an address; Write Addresses · Checked 2026-10-16
Samsara update address ↗
Update an address; Write Addresses · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Direct/private integration routes use customer-authorized scoped tokens.
Samsara application distribution and review requirements ↗
Authentication/distribution options · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Vehicle updatedAfterTime supports repeated changes polling.
Samsara list vehicle records ↗
updatedAfterTime · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Endpoint rates and rate-limit retry guidance are published.
Samsara rate limits ↗
Rate Limits; 429 handling · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Updated-time filtering identifies modifications but not hard-deleted vehicle identities.
Samsara list vehicle records ↗
updatedAfterTime · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Repeat the full authorized vehicle traversal for current-state recovery; no historical/deleted record recovery established.
Samsara collection pagination ↗
Overview; hasNextPage/endCursor · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Authorized vehicle JSON leaves through the customer integration.
Samsara list vehicle records ↗
200 vehicle response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
No retrieval window or export charge at cancellation is established by these technical sources.
Samsara list vehicle records ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Portable current vehicle master records; full telemetry/history/configuration unverified.
Samsara list vehicle records ↗
List all vehicles · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Private and marketplace external fleet applications are documented.
Samsara application distribution and review requirements ↗
Integration options · Checked 2026-10-16
Rights to custom logic -
-
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Rights to native workflow artifacts and independent execution are not established.
Samsara list vehicle records ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Customer dashboard tokens carry explicit scopes, such as Read Vehicles and Write Addresses. OAuth is recommended for marketplace apps, while direct customer tokens and private integrations have separate distribution paths.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
List Vehicles returns up to 512 per page, using after/endCursor. updatedAfterTime and createdAfterTime filter the master-data collection; historical location/statistics APIs need separate review.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Direct customer fleet API token | API key | Customer | No | customer generates scoped bearer token for a direct integration; validate product/region and actual grants | 2026-10-16 |
| Marketplace OAuth integration | OAuth 2.0 | Integration provider | Yes | app registration, customer oauth authorization and certification for public marketplace listing | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The named vehicle endpoint publishes 25 requests/second. Minimum product/license entitlement and fixed API charges remain unverified; marketplace review does not establish the price of direct-token access.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /addresses creates a named geofenced address and PATCH updates one. Both require the corresponding Write Addresses grant; mutation replay safety is not established by an external ID field.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Updated-time vehicle enumeration supports overlap and snapshot rebuilding. Hard-deleted master records, telemetry retention and durable event replay remain unverified within this scope.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Updated-time filtering identifies modifications but not hard-deleted vehicle identities. | Samsara list vehicle records ↗updatedAfterTimeChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Repeat the full authorized vehicle traversal for current-state recovery; no historical/deleted record recovery established. | Samsara collection pagination ↗Overview; hasNextPage/endCursorChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Vehicle JSON provides a portable current master-data copy. It does not prove every trip, sensor history, compliance file or fleet configuration can be reconstructed independently.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers and partners can build external fleet integrations. Native rule definitions and their rights remain unresolved (marketplace certification applies to distribution, not data completeness).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Vehicle master records return JSON under Read Vehicles. | Samsara list vehicle records ↗List all vehiclesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. after/endCursor traversal supports up to 512 vehicles per page. | Samsara list vehicle records ↗limit; afterChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. updatedAfterTime and createdAfterTime filter the collection. | Samsara list vehicle records ↗Query ParamsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. The integration guide explicitly allows privately distributed customer-token integrations. | Samsara application distribution and review requirements ↗Authentication/distribution options; Manual TokensChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | Samsara list vehicle records ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Samsara list vehicle records ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Address creation and the separately reviewed update operation require Write Addresses. | Samsara create address ↗Create an address; Write AddressesChecked 2026-10-16 Samsara update address ↗Update an address; Write AddressesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Direct/private integration routes use customer-authorized scoped tokens. | Samsara application distribution and review requirements ↗Authentication/distribution optionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Vehicle updatedAfterTime supports repeated changes polling. | Samsara list vehicle records ↗updatedAfterTimeChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Endpoint rates and rate-limit retry guidance are published. | Samsara rate limits ↗Rate Limits; 429 handlingChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Authorized vehicle JSON leaves through the customer integration. | Samsara list vehicle records ↗200 vehicle responseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. No retrieval window or export charge at cancellation is established by these technical sources. | Samsara list vehicle records ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Private and marketplace external fleet applications are documented. | Samsara application distribution and review requirements ↗Integration optionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Rights to native workflow artifacts and independent execution are not established. | Samsara list vehicle records ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedSamsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. Portable current vehicle master records; full telemetry/history/configuration unverified. | Samsara list vehicle records ↗List all vehiclesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.