Reference · built on requestConnectorFleet & telematics

Geotab

Device positions, trips, engine faults, and exception events from a MyGeotab database through the SDK's Get and GetFeed methods.

Request accessPricing ↗

About

Geotab makes the GO telematics device and runs MyGeotab, the database each fleet's data lands in. The MyGeotab SDK is a JSON-RPC API served from the /apiv1 path of your MyGeotab server. Authenticate returns a server path and session credentials. Get answers bounded queries. GetFeed hands you a checkpointed stream of new records for devices, trips, positions, engine measurements, faults, rules, and maintenance.

Through Fibric, an operator advances a GetFeed cursor for the entities it watches and proposes an Add or Set for a zone, a rule, or a user. Each proposal waits for your approval and is written once, with a receipt of what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from Geotab and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Device positions from LogRecord and DeviceStatusInfo, streamed with GetFeed and its fromVersion and toVersion tokens
  • Trips, FillUp, FuelUsed, and ChargeEvent records, which GetFeed returns as new and updated calculated data
  • Engine measurements and faults as StatusData and FaultData records keyed to a Diagnostic
  • ExceptionEvent records generated when a Rule's condition tree is violated, including Stock, Custom, and ZoneStop rules
  • DutyStatusLog, DVIRLog, and DriverChange records for hours of service, inspections, and who was driving
  • Zone, Route, User, Group, and Device master data through Get, with resultsLimit and PropertySelector

Proposed actions

  • Target capability: propose a new Zone, Rule, or User through Add, scoped to the Groups you name
  • Target capability: propose a change to a Device, User, Zone, or Rule through Set, which takes the complete modified entity

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Route a fault to the right shop

    FaultData arrives on the feed with its Diagnostic and device. The operator groups repeat faults per vehicle and proposes a service booking with the evidence attached.

    With Vehicle Fault

  • Cut idling without nagging

    An idling Rule produces ExceptionEvent records per device. The operator totals them by driver and site and proposes which ones deserve a conversation this week.

    With Idle Watch

  • Close unidentified driving

    DriverChange and LogRecord data show trips with no driver assigned. The operator proposes the likely driver from shift and key data, for a supervisor to confirm.

    With Unassigned Driving

  • Watch hours before they run out

    DutyStatusLog records give each driver's status timeline. The operator projects remaining time against planned work and proposes a reassignment where the plan will not fit.

    With Driver Hours

Requirements

  • A MyGeotab database and a user created for the integration, with only the security clearances and data-access groups the use case needs
  • TLS 1.2 or later; requests go over HTTPS to the /apiv1 path and follow the server path returned by Authenticate
  • Session handling that reuses the sessionId instead of authenticating before every call
  • For writes, awareness that API writes change the selected database immediately
Authentication
A dedicated MyGeotab API user in your database. Authenticate takes userName, password, and database, and returns a server path plus credentials with a sessionId that you reuse for later calls.

Limits

  • A session lasts 14 days, ends when the user's password changes, and an account may hold at most 100 concurrent sessions
  • Rate limits apply per method, entity, username, and database, tiered by tracked assets; exceeding one returns OverLimitException with Retry-After
  • Authenticate, CreateDatabase, SetUserPassword, and DeviceShare keep fixed base limits regardless of tier
  • Results reflect the authenticated user's access, and values come back in metric units such as km/h and meters

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Geotab ↗

Questions and answers

What is GetFeed and how does it differ from Get?
Get answers a bounded query. GetFeed is the method Geotab names as the primary way to sync data: you pass a fromVersion token and receive new records plus a toVersion to persist for the next call. Active entities such as LogRecord return new records; calculated ones such as Trip and ExceptionEvent return new and updated records.
How are rate limits calculated?
Per unique combination of method, entity, username, and database, multiplied by a tier based on tracked assets: 0 to 1,000 assets is x1, 1,001 to 10,000 is x5, 10,001 to 25,000 is x15, and 25,001 or more is x25. Responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers.
Which server do requests go to?
Authenticate returns a path, either a server name or ThisServer. Send later calls to that server's /apiv1 endpoint and reuse the credentials it returned. Where possible, use ExecuteMultiCall to bundle several requests into one HTTP call.
Ask about Geotab

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Geotab through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy