Hey <a data-id="7427" data-value="Fleetoffoot" data-denotation-char="@" href="/user/fleetoffoot" class="text-decoration-none mention">@Fleetoffoot</a> ! Sorry to hear that the API servers went down and impacted your integrations. When there's a planned change, we share updates to the Integrators Group here in the Geotab Community (which you can sign up for on your profile - let me know if you need any help). But for unexpected outages, I believe the Current Known Issues page is the best place to find this information. There's a chance the outage you experienced had just not been reported yet. However, let me double check with the team and follow up with you once I have confirmation as there have been several changes this year. Also, I know that the development team has been looking into how to improve messaging around our API and server statuses, so if you are interested in having your name added to the research panelist list please let me know? Warm regards, Gen

View Current Geotab Server Status

<a data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" href="/user/lppapillon-1145" class="text-decoration-none mention">@LPPapillon-1145</a> Thank you, I will look into what hardware we are using.

Issues getting certain fields though Geotab api

Hey <a data-id="8256" data-value="AtaydeMM-8256" data-denotation-char="@" href="/user/ataydemm-8256" class="text-decoration-none mention">@AtaydeMM-8256</a> ! Great questions and thanks for the detailed post! The public documentation doesn't describe how the modem connection record is laid out on GO Anywhere Plus, or whether the carrier code (MCC&#x2F;MNC) is exposed through DebugData, StatusData or another endpoint. It's possible the payload format differs between GO9 and GO Anywhere Plus firmware, which could explain what you're seeing. I'll reach out to the team and follow up with you as soon as I hear back. Warm regards, Gen

How to extract MCC/MNC (Carrier Info) from GO Anywhere Plus devices?

<a data-id="11754" data-value="Charlie_5" data-denotation-char="@" href="/user/charlie_5" class="text-decoration-none mention">@Charlie_5</a> I think there is another option here that does not need a pipeline or a database. I build MyGeotab add-ins for Fleet Wolf customers, and they run on the API. The API gets to the detail you are missing in the Data Connector. Trips, exception events, faults, status data. The add-in pulls what it needs when the page opens and shows the result right inside MyGeotab. That also helps with your concern about moving data around. An add-in runs under the login and permissions of the person using it, so nothing gets copied to a separate database and there is no database to maintain. Mine are a single HTML page with a short config that points to it. It is not the right tool for everything. If you want years of history or heavy analysis across millions of records, you will run into API limits, and I think the API Adapter Tucker suggested is the better fit. Where the API works best is answering what needs attention today, for the person who has to act on it. It is still building something, and I know you said that is outside your regular job. But you mentioned having something you want Geotab to see. An add-in would let you show them working reports on real data, and that is harder to ignore than a feature request. I think that is a better chance of changing the system than waiting on the Data Connector.. I have worked with several systems out there, we are pretty fortunate in how this was set up years ago for where we are today. Couple screen shot examples. <img class="ql-image" src="/forum/plugins/gcs-uploads/files/1793488060118-image.png"/> <img class="ql-image" src="/forum/plugins/gcs-uploads/files/1793488230961-image.png"/>

Better data, less filler

<a data-id="1051" data-value="Genevieve-1051" data-denotation-char="@" href="/user/genevieve-1051" class="text-decoration-none mention">@Genevieve-1051</a> Thank you!

How do I find device plan "Asset" with ID 55

<h1> </h1>Hello Integrators, Starting Monday, November 9, 2026 the Data Intake Gateway (DIG) will apply a rate limit to the &#x2F;records endpoint. The limit keeps ingestion stable and fast for everyone by stopping any single integration from using too much capacity during a sudden traffic spike.<h2>What's changing</h2><ul><li>POST &#x2F;records will be limited to 1,000 requests per minute.</li><li>As with DIG's existing rate limits, the limit is counted against both your DIG user account and your source IP address. A request that goes over either one is rate limited.</li><li>The limit counts requests, not records. A request is counted the same whether it carries one record or many.</li><li>Rate-limited requests receive HTTP 429 TOO_MANY_REQUESTS with a Retry-After header (RFC 6585). Records in a rate-limited request are not accepted and must be sent again.</li><li>Nothing else changes: request and response formats, the &#x2F;invalidrecords endpoint, and the existing authentication limits stay the same.</li></ul><h2>Who may be affected</h2>The limit is set well above typical integration traffic and is meant as a safeguard against sudden spikes. Integrations that batch their records are unlikely to be affected. Please review your integration if you:<ul><li>send many small requests, for example one request per device or per record, instead of batching records together</li><li>run several DIG user accounts from the same source IP address, because these share one IP limit</li><li>expect a big increase in device count or reporting frequency, or plan to load large amounts of historical data</li></ul><h2>What you should do</h2><ol><li>Handle 429 responses. Wait the number of seconds given in Retry-After, then send the same request again. Don't treat a 429 as a permanent failure, and don't drop the records.</li><li>Back off with jitter. Add a small random delay to retries so queued requests don't all retry at the same moment.</li><li>Batch your records. We recommend 200–500 records per request on average. At 500 records per request, 1,000 requests per minute allows up to 500,000 records per minute.</li><li>Pace large loads. Spread out historical loads and catch-up after an outage instead of sending as fast as possible.</li></ol><h2>Questions</h2>If you have questions about this change or for any resulting production issues, please submit a support ticket through MyAdmin. Or ask on this thread below!

Upcoming change: Rate limiting on the Data Intake Gateway (DIG) /records endpoint

<a data-id="1143" data-value="DFenn-1143" data-denotation-char="@" href="/user/dfenn-1143" class="text-decoration-none mention">@DFenn-1143</a> Geotab has been recommending to migrate away from using Trailers and TrailerAttachment in favor of Devices and DeviceLink. Give that a shot and see if it does what you need: https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;apiReference&#x2F;objects&#x2F;DeviceLink&#x2F;

How do I associate a Trailer to a DutyStatusLog?

<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 in MyGeotab SDK

Hi Eishi and Felipe, thank you both for your responses and for looking into this. @Felipe_Hoffa, to answer your question: we are looking to interpret the sequence of events for device cellular connectivity health monitoring, specifically to calculate accurate uptime and availability metrics. To give you a bit more background on our current process, we have been using a report template from the &quot;Log Data and Collisions&quot; module, and recently implemented a script that queries <code>debugData</code> via the MyGeotab API. I appreciate any insights you and the MCP team can share on this!

Extracting DebugData (debug records) via the MyGeotab MCP Connector

hi Geotab devices don't natively send TAIP messages. To integrate them into a computer-aided dispatch (CAD) system, you need to use middleware: 1. Pull the positions from the Geotab cloud using the Data Feed API (the 'GetFeed' method for 'LogRecord'). 2. Convert that data to the TAIP format in your middleware. 3. Send the converted messages to the CAD system.

Dispatch MyGeotab Integration

<a data-id="12250" data-value="richardprater" data-denotation-char="@" href="/user/richardprater" class="text-decoration-none mention">@richardprater</a> Geotab supports SSO via SAML 2.0. Here are the docs: <a href="https://docs.google.com/document/d/1HlFpXjG09JOaRaf7ocXGEPsWVDGvjWOofz18h8DZL18/edit#heading=h.6gqkmkwes4dm" target="_blank">MyGeotab SAML 2.0 SSO Integration Guide</a> For your other questions:<ol><li>`trip.distance` is in km: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/Trip/index.html" target="_blank">https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;apiReference&#x2F;objects&#x2F;Trip&#x2F;index.html</a></li><li>Check out the FuelTaxDetail documentation: <a href="https://developers.geotab.com/myGeotab/apiReference/objects/FuelTaxDetail/index.html" target="_blank">https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;apiReference&#x2F;objects&#x2F;FuelTaxDetail&#x2F;index.html</a></li><li>This one I'm less sure of. I know you can select demo vocations and demo vehicles, but I don't know that they cover your specific requirements. This document might help you: <a href="https://support.geotab.com/help/mygeotab/access-and-administration/getting-started/database-setup#ariaid-title4" target="_blank">https:&#x2F;&#x2F;support.geotab.com&#x2F;help&#x2F;mygeotab&#x2F;access-and-administration&#x2F;getting-started&#x2F;database-setup#ariaid-title4</a></li></ol>

Third-party app for owner-operators: OAuth/delegated access, or a service-account user?

It was my understanding that, although the standard&#x2F;free versions of Gemini do not directly support MCP connections, the Enterprise - Business version does support them (as a &quot;Pre-GA&quot; feature). I may be missing something, so I'll provide a link for reference: https:&#x2F;&#x2F;support.google.com&#x2F;g&#x2F;answer&#x2F;17106276?hl=en Thanks!