Hi Team,We pull data for our fleet via the API. We call teh various api endpoints on a daily basis and ask for the last 48 hours of data, so every day there is an overlap of 24 hours in case any data is missed.Even doing that though, often we find that if we go back at month end and pull the whole month we fill in gaps with missing data. What's the best method of pulling the data from the geotab datasets to avoid this? We pull a lot of different callsevents, trips, odometers, engine hours, log status, etc etc. Would really appreciate knowing how we can pull the data using a reported date instead of the event date so we know we've got everything, thanks 

Method of get late reporting assets

Where can I find my credentials to connect Highway with my GeoTab

Hello. Recently, a customer has reached out asking if this is possible to have a plan or configuration that allow to have GO device data to be extracted to a third party software (customer's internal management software), but without having MyGeotab UI. I believe that due to security and quality reasons, it might not be possible. But just wanted to confirm.

No-software plan

We have 2 integrations that generate PDFs from an add-in in Geotab Drive, and to do it, we leverage this kind of link: https://my.geotab.com/test_database/#hosLogs,dateRange:(endDate:'2019-10-28T17:46:00.885Z',startDate:'2019-10-14T04:00:00.000Z'),driver:b12345,includeExemptions:!f,includeIntermediateLogs:!f,token:('userName':'johndoe','sessionId':'asdasdasdasdasdasdasd','database':'test_database') This has worked for 6+ years. Today when we generate the PDFs, customers have started getting blank pages. When I try to replicate in chromium locally, I am directed to the login screen. Has support for this kind of link been revoked?I tried to workaround the issue by setting geotabAPI_credentials and geotabAPI_server in localStorage, then navigating to the base URL, but still I am getting directed back to login. This might be related to the move to CIAM and oauth, but there was no communication around this change and support being removed. We use this daily and 30K+ drivers depend on it for compliance. Please advise.

Support for passing session token in URL removed??

Hello Geotab Support Team,We are integrating an external fleet management system with Geotab. We can read DVIR defect data, but we are unable to update the defect status in Geotab.Our goal is to push updates such as repaired or closed defects (stored in our internal system) into Geotab.We need confirmation on the following points: What is the correct object to update DVIR defects, DVIRLog or DVIRDefect What is the required API payload to update repairStatusType, repairDateTime, repairUser and repair notes Are there any required permissions or workflow constraints Do you have a working API example for updating a DVIR defectWe want to ensure proper synchronization between our system and Geotab for defect lifecycle management.Thank you for your support.

MyGeotab API support request to update DVIR defect status from external system

Hi all, Building a Charge Point/Energy Management System integration with MyGeotab. The demo DB we're developing against is all ICE, so we can't exercise the EV side (SoC, ChargeEvent, FuelAndEnergyUsed, EV diagnostics). Is there a partner-accessible demo or sandbox DB with EVs? Or has anyone solved this another way? Thanks,Ryan

MyGeotab Demo database with EV vehicles for integration testing?

We were notified by a customer a few days ago that they were experiencing some issues with our Geotab integration, and after some investigation, we determined that Rule Notification web requests started coming in with the "text/plain" Content-Type header, instead of "application/x-www-url-formencoded" as they usually do. This caused cascading failures for many of our customer integrations and required us to override the Content-Type header in API forwarding middleware wherever possible. The only event we've noticed that seems to correlate to that change is a database update from 11333.561 to 11333.585. The update was completed ~90 seconds after our telemetry indicates that the first webhook failures started. Is this an intentional change to the Content-Type header of notification web requests in a recent update, or should we be reporting this as a bug? I've tried to find release notes or other documentation specific to database version 11333.561 (or any database version, for that matter) but could only find info for general MyGeotab releases.

Web Request Notification Template Content Type Changed Unexpectedly

when we create a new database, we also add API's for the tachograph files to be sent to our other service provider Convey. Historically we were able to create and add a password to Convey and they would request the API. This was working all good. But I have been advised that we cannot setup passwords now and hence trying to fix this. So please advise as without password Convey cannot access the API 

How to set up API links for tacho analysis

Hello, We have been experiencing intermittent issues doing Fuel Transaction Imports since Tuesday Oct 7, 2025.  What's unusual about these is that we are authenticating fine, however, when we try to send the Fuel Transaction, we are getting a InvalidUserException after we have authenticated. I would have expected a InvalidPermissionsException, but not a InvalidUserException.  We can read Devices and Users with no authentication issues. Some of our partners have been seeing the same issue.Any ideas? Thanks,Jon 

Experiencing intermittent issues doing a Fuel Transaction Import

Hello All, I am making this post to field any and all possible information on the upcoming DeviceLink changes. We've implemented the DVIR Trailer changes within our integration (https://community.geotab.com/s/feed/0D5Pd00000izS7oKAE) and while making those changes considered the Trailer and Trailer Attachment depreciation notices. Several posts have been referencing the changes since 2022 "Starting from 10.0 "DeviceLink" will be introduced as a replacement." I am struggling to find the exact documentation at this time, but I thought that I had read that some of these changes were going to start releasing this October '25. If that's true, we believe it would be important to implement the changes beforehand to prepare for the updates. Testing with DeviceLink (Could not find specific documentation) I am able to create, retrieve and remove these objects via the API. When creating a Device Link between a Tractor and Trailer, I am also able to see the link displayed under the Tractor's Profile within the Geotab Platform. However, one of our biggest concerns is the Driver Log Display. With Trailer Attachments, the Tractor and Trailer information, when linked to a driver, displayed under the driver's HOS logs. With a DeviceLink, we've been unable to reproduce this functionality or see the links within the Geotab Drive application experience. Any additional information, insight or guidance into these new features would be much appreciated. Thank you kindly for your time in advance!

DeviceLink Changes &amp; Implementation Assistance

DeviceLink Changes & Implementation Assistance

On 9/3/2021 at Approx 13:34 Hours -6 UTC, my Custom CURL based Endpoint Fetching using the API Ednpoints to store into my MySQL Database stopped being able to receive Truck locations and some other info. My Cronjob returns completely blank data now on Truck locations and incomplete or no data on a few other things, like old odo readings was noticed. Not sure yet with the fall out what other functions are also failing. Our customers cannot track Freight on our Web System without updates coming in. The developer who wrote all of this is long gone working at Big Corp X and using a Custom Solution from 2017 is dangerous without full documentation and with Geotab constantly evolving. We need a budget friendly solution to modernize our integration. **Edit - Removed PHP Code for privacy now that situation is "resolved"?

Geotab API Endpoints Truck Location Tracking suddenly not working

We have a v1.1 api integration that within the last few months, sadly as I am stepping in to this with the workers not giving me solid data just an “oh by the way”, we don't have an exact date - it either started after some php 7.4 change ups from 5.6 end of May but more than likely before than.i have just reset the system user credentials as I read that an April update changed some permission structures and that might've been the issue, that did not resolve. before sharing code and logs maybe this already rings a bell? The trailers are untracked assets and when a driver does a write up on their geotab for it, a maintenance request used to be logged in our system with the api setup we have. Now it is not, notably I believe it is only for tire maintenance as that is the only ones I've been told don't work / only issues needing write up. When they asked a driver to test they didn't entertain and and do a few different kind but that may need to happen. I can navigate the database errrors and such but am not a php developer so am outsourcing that to someone who doesn't know what to do to assist, what should I be directing them to look for or who can I contact when geotab doesn't help customers directly on api issues anymore? The original developer of this API is no longer available to contact and I am thinking it is some of the changes this year in the geotab asset management and his api causing this and we need to adjust 