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
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Get exposes structured Device and LogRecord objects within the authenticated database and clearances.
MyGeotab Get method ↗
typeName, search, credentials and return value · Checked 2026-10-17
Bulk delivery 8.8/10
Batched or iterable API requests
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
GetFeed version zero traverses the earliest available records; drain batches with toVersion until caught up.
MyGeotab Data Feed synchronization ↗
How the version token works; Dealing with volume · Checked 2026-10-17
Query expressiveness 8.8/10
Documented structured API filters
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Get has entity-specific search and supported sorting/pagination; feed searches are not a general filtered query interface.
MyGeotab Get method ↗
Search and sort parameters · Checked 2026-10-17
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Current provider navigation explicitly describes free SDK/API tools; subscribed hardware and data features are separate entitlements.
Geotab SDK/API customer integration route ↗
Integrations: Developer SDK & API, free API and SDK tools · Checked 2026-10-17
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
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
The integration toolkit permits solutions to use customer-database service accounts outside user sessions; marketplace distribution is separate.
Geotab integration service accounts and group scope ↗
Service Accounts; How do I make API calls outside of a user’s session? · Checked 2026-10-17
Downstream permission -
-
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Technical service-account authorization does not by itself establish contractual AI-use, redistribution or other downstream rights.
Geotab integration service accounts and group scope ↗
Service Accounts; user scope and clearances · Checked 2026-10-17
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
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Zone supports Add and Set to create and update geofences; Zone calls must be issued sequentially.
MyGeotab Zone create/update contract and limits ↗
Introduction; Add and Set rate-limit rows; Zone fields · Checked 2026-10-17
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Customers and integrators can build custom SDK applications using authorized database access.
Geotab SDK/API customer integration route ↗
Develop custom applications; Flexibility and control with our open platform · Checked 2026-10-17
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
GetFeed returns new and modified entity versions and provides a consumer-maintained version token; this is not database CDC.
MyGeotab GetFeed limits and entity support ↗
fromVersion; FeedResult · Checked 2026-10-17
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Method/entity quotas and batch limits are published. Over-limit responses require bounded backoff; mutation outcomes need reconciliation.
MyGeotab reliable reads, writes and recovery ↗
Handling failures; Managing authentication · Checked 2026-10-17
MyGeotab GetFeed limits and entity support ↗
GetFeed: 60 requests per minute unless entity-specific; resultsLimit · Checked 2026-10-17
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Versioned feeds identify new/updated records. Universal Device/LogRecord deletion identities and recovery of purged payloads are not established.
MyGeotab GetFeed limits and entity support ↗
fromVersion; supported entity types · Checked 2026-10-17
Replay and gap recovery 10.0/10
Consumer checkpoint with documented retention limits and resnapshot recovery
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Persist toVersion after durable processing; lost tokens can restart from version zero or an initial supported date. Recovery is limited to data retained under configured purge schedules.
MyGeotab Data Feed synchronization ↗
How the version token works: durable checkpoint; lost-token recovery · Checked 2026-10-17
MyGeotab data purge categories and retention settings ↗
Default two-year retention; category-specific schedules up to eight years · Checked 2026-10-17
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 10.0/10
Feed into a customer-controlled store
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
The provider explicitly supports pulling fleet feeds into the customer’s environment for synchronization with other applications.
Geotab SDK/API customer integration route ↗
Real-time data and synchronization · Checked 2026-10-17
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Purge settings describe live-database retention, not a contractual service-cancellation retrieval window.
MyGeotab data purge categories and retention settings ↗
Data purge; Data purge categories · Checked 2026-10-17
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
GetFeed returns portable records; nested references require separate retrieval, and purged data and whole-service configuration are outside the established copy.
MyGeotab Data Feed synchronization ↗
Caching to improve performance; available records · Checked 2026-10-17
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 5.0/10
Customer-editable native workflows or agent configurations
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Customers create native fleet rules and edit conditions, including the advanced conditions editor.
MyGeotab native custom rules ↗
Creating rules based on vehicle type; Creating an idling rule · Checked 2026-10-17
Rights to custom logic -
-
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Custom-rule instructions do not establish ownership, reusable export or independent execution rights for native rule definitions.
MyGeotab native custom rules ↗
Native custom rules and advanced conditions · Checked 2026-10-17
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
A dedicated customer-database service account authenticates to obtain a session ID. Security clearances and data-access groups govern results. This integration route is separate from optional marketplace distribution and its partner process.
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
Get supports entity-specific filters and documented sorting/pagination. GetFeed starts at version zero for available records and advances using toVersion. Device batches have a 5,000-record maximum; LogRecord batches have a 50,000-record maximum. Nested entities often supply IDs only.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer database service-account session | session | Customer | No | dedicated user in the customer database; authenticate obtains sessionid and server path. clearances and data groups apply. root companygroup scope required for full-fleet logrecord feeds; use bounded get for restricted data. optional marketplace listing is separate. | 2026-10-17 |
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 provider describes its SDK/API tools as free. Devices, subscribed services and entity features still determine available data; no hardware or base-plan price is presented as an API fee.
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
Add and Set explicitly support Zone geofences. Set requires the current entity and its required fields, rather than assuming patch semantics. Serialize Zone mutations and reconcile uncertain outcomes before retrying.
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
Persist each entity’s toVersion only after durable processing, then resume with fromVersion. Full-fleet feeds require CompanyGroup scope; current releases reject scoped-user or device-filtered LogRecord feeds, so restricted reads need bounded Get. Data purge defaults to two years and varies by category and administrator configuration; purged records cannot be recovered by replay.
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 establishedMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Versioned feeds identify new/updated records. Universal Device/LogRecord deletion identities and recovery of purged payloads are not established. | MyGeotab GetFeed limits and entity support ↗fromVersion; supported entity typesChecked 2026-10-17 |
| How can extraction recover after missed events or an interrupted consumer? | Consumer checkpoint with documented retention limits and resnapshot recoveryMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Persist toVersion after durable processing; lost tokens can restart from version zero or an initial supported date. Recovery is limited to data retained under configured purge schedules. | MyGeotab Data Feed synchronization ↗How the version token works: durable checkpoint; lost-token recoveryChecked 2026-10-17 MyGeotab data purge categories and retention settings ↗Default two-year retention; category-specific schedules up to eight yearsChecked 2026-10-17 |
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
Get and GetFeed supply structured customer-held records, with related entities loaded separately. Rebuild from retained records using version zero or an initial supported date; the result is not a database backup or a guarantee of complete deleted or historical payloads.
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
MyGeotab users define native custom rules and conditions. Ownership and independent execution of those native definitions remain unresolved (external SDK code is a separate artifact).
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 scopeMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Get exposes structured Device and LogRecord objects within the authenticated database and clearances. | MyGeotab Get method ↗typeName, search, credentials and return valueChecked 2026-10-17 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. GetFeed version zero traverses the earliest available records; drain batches with toVersion until caught up. | MyGeotab Data Feed synchronization ↗How the version token works; Dealing with volumeChecked 2026-10-17 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Get has entity-specific search and supported sorting/pagination; feed searches are not a general filtered query interface. | MyGeotab Get method ↗Search and sort parametersChecked 2026-10-17 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. The integration toolkit permits solutions to use customer-database service accounts outside user sessions; marketplace distribution is separate. | Geotab integration service accounts and group scope ↗Service Accounts; How do I make API calls outside of a user’s session?Checked 2026-10-17 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Current provider navigation explicitly describes free SDK/API tools; subscribed hardware and data features are separate entitlements. | Geotab SDK/API customer integration route ↗Integrations: Developer SDK & API, free API and SDK toolsChecked 2026-10-17 |
| What permission is needed for the documented downstream use? | -MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Technical service-account authorization does not by itself establish contractual AI-use, redistribution or other downstream rights. | Geotab integration service accounts and group scope ↗Service Accounts; user scope and clearancesChecked 2026-10-17 |
| Which external write operations are documented? | Create and update in one business domainMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Zone supports Add and Set to create and update geofences; Zone calls must be issued sequentially. | MyGeotab Zone create/update contract and limits ↗Introduction; Add and Set rate-limit rows; Zone fieldsChecked 2026-10-17 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Customers and integrators can build custom SDK applications using authorized database access. | Geotab SDK/API customer integration route ↗Develop custom applications; Flexibility and control with our open platformChecked 2026-10-17 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. GetFeed returns new and modified entity versions and provides a consumer-maintained version token; this is not database CDC. | MyGeotab GetFeed limits and entity support ↗fromVersion; FeedResultChecked 2026-10-17 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Method/entity quotas and batch limits are published. Over-limit responses require bounded backoff; mutation outcomes need reconciliation. | MyGeotab reliable reads, writes and recovery ↗Handling failures; Managing authenticationChecked 2026-10-17 MyGeotab GetFeed limits and entity support ↗GetFeed: 60 requests per minute unless entity-specific; resultsLimitChecked 2026-10-17 |
| Where can a usable data copy be delivered? | Feed into a customer-controlled storeMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. The provider explicitly supports pulling fleet feeds into the customer’s environment for synchronization with other applications. | Geotab SDK/API customer integration route ↗Real-time data and synchronizationChecked 2026-10-17 |
| What retrieval rights are documented at cancellation? | -MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Purge settings describe live-database retention, not a contractual service-cancellation retrieval window. | MyGeotab data purge categories and retention settings ↗Data purge; Data purge categoriesChecked 2026-10-17 |
| How can customers define their own business logic? | Customer-editable native workflows or agent configurationsMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Customers create native fleet rules and edit conditions, including the advanced conditions editor. | MyGeotab native custom rules ↗Creating rules based on vehicle type; Creating an idling ruleChecked 2026-10-17 |
| What rights or portability are documented for custom workflow artifacts? | -MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. Custom-rule instructions do not establish ownership, reusable export or independent execution rights for native rule definitions. | MyGeotab native custom rules ↗Native custom rules and advanced conditionsChecked 2026-10-17 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. GetFeed returns portable records; nested references require separate retrieval, and purged data and whole-service configuration are outside the established copy. | MyGeotab Data Feed synchronization ↗Caching to improve performance; available recordsChecked 2026-10-17 |
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
- Contractual downstream-use conditions beyond reviewed technical authorization
- Universal hard-delete identities for Device and LogRecord
- A fixed version-token expiry independent of underlying purge settings
- Native workflow artifact ownership and independent runtime
- Customer retrieval rights after cancellation
Documentation
Assessment checked 2026-10-17. Each answer retains its source and applicable route; the check date does not establish live account behavior.