<a data-id="1087" data-value="TuckerBA-1087" data-denotation-char="@" href="/user/tuckerba-1087" class="text-decoration-none mention">@TuckerBA-1087</a> I saw that and took that to mean that was the limit when using pagination. I had already switched to using pagination, but wanted get the definitive answer. So now I know. Thanks for the clarification.

Get Device is being limited to 5000 records

+1 to this point. Is there a reason that you're looking for the max version specifically? If it's just to know when to stop asking for results, I would recommend exactly what <a data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" href="/user/lppapillon-1145" class="text-decoration-none mention">@LPPapillon-1145</a>suggests and simply loop until there are no more to get. For high-activity feeds, the version is likely to be a moving target anyway - you might find the current latest record and have additional records added by the time you're done looping and processing the first batch.

Geotab SDK GetFeed call never reaches max version

Tucker's response will most likely get you what you need. You might also be able to query the API for all Devices in your database and filter them by their deviceType. That should let you identify all GO devices in your database without needing to try and parse out their serial numbers.

How to identify GO Devices with the C# SDK?

Hi <a data-id="11643" data-value="jkwong" data-denotation-char="@" href="/user/jkwong" class="text-decoration-none mention">@jkwong</a> , welcome to the Community! We are glad you are here! The enriched fields are available as properties of the MyGeotab FaultData API object, including: - severity - riskOfBreakdown - failureMode - faultDescription - recommendation - effectOnComponent You can request them using Get or GetFeed for FaultData. However, these fields may be null when enrichment is unavailable for a particular fault. The API documentation confirms that the fields exist, but does not guarantee that every value shown in the MyGeotab UI will be populated for every Noregon-enriched record. I recommend testing the API against a known enriched fault and comparing the response with the corresponding record in MyGeotab. The current API reference is available here: https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;apiReference&#x2F;objects&#x2F;FaultData&#x2F; Hope that helps! Eishi FUN

GeoTab Fault Data - Enriched with Noregon - API Access?

<a data-id="11959" data-value="bikiran" data-denotation-char="@" href="/user/bikiran" class="text-decoration-none mention">@bikiran</a> Thank you for following up when you found the answer. We appreciate this contribution to the communities collective knowledge. Please feel free to reach out if you ever have any other questions.

MyGeotab API: Add zoneType instead of zone while adding new custom Rule

<a data-id="8083" data-value="mdevol" data-denotation-char="@" href="/user/mdevol" class="text-decoration-none mention">@mdevol</a> I think its probably best to make a support ticket here and dig into it a little more so we can see whats going on.

Trailer devices with TmpTrailerID set to null

Hey <a data-id="6441" data-value="eiler-6441" data-denotation-char="@" href="/user/eiler-6441" class="text-decoration-none mention">@eiler-6441</a> , Hi, great question and one that is worth investigating properly. I think I know what is going on here based on some recent changed with MyGeotab logins. What you are probably experiencing is related to the Unified Login rollout which is a centralized identity platform that new databases are now on by default. Older databases use a legacy per-database authentication model where the username and email were effectively the same field, but new databases on Unified Login enforce a separation between the local username and the email identity. This change is what is causing the inconsistency you are seeing between old and new companies. For integrators creating users via the API against new databases, the handling is different and the current documentation may not fully reflect this yet. I would recommend: 1. Reviewing the Unified Login overview (https:&#x2F;&#x2F;support.geotab.com&#x2F;help&#x2F;mygeotab&#x2F;access-and-administration&#x2F;log-ins&#x2F;unified-login-overview) for context on how the new identity model works 2. Opening a support ticket so our team can advise on the correct API approach for creating users on Unified Login databases — this is a technical integration question that needs specific guidance We want to make sure this is properly documented for developers. Thank you for flagging it. Have a great day! Eishi FUN

API Error

<a data-id="1451" data-value="Sajad-1451" data-denotation-char="@" href="/user/sajad-1451" class="text-decoration-none mention">@Sajad-1451</a> Thank you! That is helpful context regarding generous API limits. The release of those skills should make this MCP much more useful&#x2F;impactful.

MCP - GetDirections, GetFeed, etc...

⚠️ Transition Away from Legacy EV Data Endpoints In the early days of fleet electrification, we developed three original API endpoints to provide trailblazing companies access to Geotab-calculated EV insights. We now have better data objects that deliver the same insights in a more accurate and scalable way. These legacy endpoints are no longer officially supported. We strongly encourage our partners to transition to the new data objects by early 2026 to ensure seamless operation and avoid disruptions. Legacy Endpoint Deprecation Schedule The following legacy endpoints will be deprecated and should be replaced by the suggested data objects:<ul><li>GetBatteryStateOfHealth<ul><li>Deprecation Target: September 26, 2026</li><li>Suggested Replacement: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/BatteryStateOfHealth/index.html" target="_blank">BatteryStateOfHealth</a></li></ul></li><li>GetRangeCapability<ul><li>Deprecation Target: September 26, 2026</li><li>Suggested Replacement: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/RangeEstimate/index.html" target="_blank">RangeEstimate</a></li></ul></li><li>GetRealTimeRange<ul><li>Deprecation Target: September 26, 2026</li><li>Suggested Replacement: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/EVStatusInfo/index.html" target="_blank">EVStatusInfo</a></li></ul></li></ul> ✨ What's Better About the New Data Objects? The new data objects are superior to the legacy endpoints they replace, offering significant advantages:<ul><li>Better Performance: Get results up to 10x faster than legacy endpoints.</li><li>More Accurate Results: Our updated EV range model provides greater precision. The RangeEstimate object has confidence intervals to represent the level of certainty in the calculated EV range.</li><li>More Options for Requesting Results: The new data objects are compatible with the standard Get() method and DeviceSearch. This allows you to use Geotab-standard search criteria to return the specific results you need, for the devices you want.</li><li>More Useful Information: In addition to real-time range, EVStatusInfo now includes an estimate of the charge complete time, helping you predict when an EV will finish charging.</li></ul> 💡 Help Is Available Need assistance working with the Geotab API, including the latest EV data objects?<ul><li>Everyone can post questions to the Integrator's Hub on Geotab community.</li><li>Fleet customers can send questions to their reseller partner.</li><li>Resellers and marketplace partners can send questions to their solutions engineering contact or partner account manager.</li></ul>Useful Resources<ul><li><a href="https://www.google.com/search?q=https://www.geotab.com/support/electric-vehicle-data-diagnostics-and-api-user-guide" target="_blank">Electric Vehicle Data Diagnostics and API User Guide</a></li><li><a href="https://www.google.com/search?q=https://developer.geotab.com" target="_blank">Developer site</a></li><li><a href="https://docs.google.com/document/d/1gFtXqnZEtyERUj47gnzW12itF-I-lERDgvpiPWchc38/edit?usp=sharing" target="_blank">EV Data Over API - Transition away from legacy endpoints DOC</a></li></ul>

📣EV Data API Legacy Endpoint Deprecation 📣 : September 26, 2026

<a data-id="1087" data-value="TuckerBA-1087" data-denotation-char="@" href="/user/tuckerba-1087" class="text-decoration-none mention">@TuckerBA-1087</a>- More sections to link to the finer details. It might be just how the new Development pages are generated, but the current method used to create a Table of Contents is very inconsistent. Sometimes it uses details tags, other pages use section tags and header tags, and barely used at all. For this feedback generally, a link to https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;guides&#x2F;goDeviceLogging&#x2F;index.html#odometer, resolving to the odometer header, would be great as a direct link. Similar issues with the TOC existing on other pages, like https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;addIns&#x2F;developingAddIns From what I can see, several pages have not been updated to match the new requirements compared to when it was hosted on GitHub Pages, back in the day.

Developer Documentation Improvement - GO Device Logging

Hey <a data-id="8083" data-value="mdevol" data-denotation-char="@" href="/user/mdevol" class="text-decoration-none mention">@mdevol</a> thanks for reaching out and sorry has interrupted you again let me talk to the team who worked on this and see what they say. I will let you know what I hear from them as soon as I do!

Getting PlatformNotSupportedException when authenticating to GeoTab

With a lot of the documentation on the MyAdmin API being updated to V3, is there also a plan to update the runner and the Using With JavaScript downloads to be more V3 compliant?  This would allow testing pagination and other new features V3 is intended to provide.  Is there any possibility of having an API client similar to the Geotab JavaScript client (https://github.com/Geotab/mg-api-js) created for the MyAdmin APIs? While I know the possible usage scope is a little different, and working on my own MyAdmin API class is likely a time sink that I would be interested in undertaking. Something more official in the long term would be nice 