<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?

Google does believe in MCP and is investing heavily in the protocol. The issue is that it still hasn't released support in Gemini, as a chat&#x2F;assistant, for connecting directly to an external MCP server. That's why, for now, we recommend using Geotab MCP with Claude, ChatGPT, or Copilot, which already have the MCP client experience built in. Google is clearly moving in that direction; they've simply been slower to bring it to Gemini. In the meantime, Google does offer MCP client support through its developer tools, including Antigravity and the Gemini&#x2F;Antigravity CLI. They're also adding MCP support to other parts of the Gemini API and Google Cloud. Google docs: Antigravity &#x2F; Gemini CLI + MCP: <a href="https://docs.cloud.google.com/mcp/configure-mcp-ai-application" target="_blank">https:&#x2F;&#x2F;docs.cloud.google.com&#x2F;mcp&#x2F;configure-mcp-ai-application</a> Antigravity CLI + MCP: <a href="https://docs.cloud.google.com/cloud-assist/design-deploy-antigravity-cli" target="_blank">https:&#x2F;&#x2F;docs.cloud.google.com&#x2F;cloud-assist&#x2F;design-deploy-antigravity-cli</a> Gemini API + remote MCP: <a href="https://ai.google.dev/gemini-api/docs/function-calling" target="_blank">https:&#x2F;&#x2F;ai.google.dev&#x2F;gemini-api&#x2F;docs&#x2F;function-calling</a>

Gemini availability for Geotab MCP Connector

<a data-id="1044" data-value="EishiFUN" data-denotation-char="@" href="/user/eishifun" class="text-decoration-none mention">@EishiFUN</a> It is kind of documented here - https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;guides&#x2F;myGeotabUrls&#x2F;#credentials - but it doesn't give any direct example of passing the session ID into the URL but it is possible to do for like a Kiosk login senario. <a data-id="1143" data-value="DFenn-1143" data-denotation-char="@" href="/user/dfenn-1143" class="text-decoration-none mention">@DFenn-1143</a>It doesn't given an example of how a session ID should be added, and with since the introduction of <a href="https://www.geotab.com/blog/centralized-identification-access-management/" target="_blank">CIAM</a> and <a href="https://support.geotab.com/help/mygeotab/access-and-administration/log-ins/unified-login-overview" target="_blank">Unified Login</a> password management has been removed from the MyGeotab database level all to gether. Unless the user account doesn't have an email address (they still need to have a unique username in CIAM though, and conflicts for usernames like &quot;JohnSmith&quot; are lot more possible). As <a data-id="1087" data-value="TuckerBA-1087" data-denotation-char="@" href="/user/tuckerba-1087" class="text-decoration-none mention">@TuckerBA-1087</a>mentioned it might be easier to integrate SAML SSO into your application use that method to access the Geotab portal. Depending on how you're displaying the portal in the application it my prevent access if doing it through an iFrame in a browser-like application - https:&#x2F;&#x2F;developers.geotab.com&#x2F;myGeotab&#x2F;guides&#x2F;myGeotabUrls&#x2F;#embedding-myg-in-iframe

Auto-Login using URL Integration

+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

Hey <a data-id="11923" data-value="shanegraham" data-denotation-char="@" href="/user/shanegraham" class="text-decoration-none mention">@shanegraham</a> I wanted to follow up with you on this question after I talked with our SDK team about this. OAuth is a known direction for MyGeotab integrations, and the team intends to document and officially support it for public use. However, that work is not complete yet, and there is currently no confirmed timeline for when the public documentation and supporting automation will be available. Because of that, I would treat the OAuth credential type as experimental for now. It may work in production if you have already configured and tested it successfully, but it is not yet an officially documented or supported integration path. There is also a possibility that the current implementation could change before the supported public version is released. If your integration requires a fully supported production authentication method, I would recommend holding off for now or continuing to use the currently documented authentication approach. Hope that helps! Eishi FUN

Now that geotab supports OAuth is it to early to add it to our integrations

<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

Hi <a data-id="1203" data-value="Gus_Rubio10" data-denotation-char="@" href="/user/gus_rubio10" class="text-decoration-none mention">@Gus_Rubio10</a> , great question thank you for asking it here in our community! The Geotab Data Connector officially supports the following tools: Microsoft Power BI, Microsoft Excel (via Get Data&#x2F;Power Query), and Tableau. Looker Studio is not on the officially supported list. That said, the connector uses an OData connection, so it may technically work with other tools that support OData — but those tools haven't been officially tested and wouldn't be eligible for support if you run into issues. For full details, the Geotab Data Connector documentation (https:&#x2F;&#x2F;support.geotab.com&#x2F;help&#x2F;mygeotab&#x2F;industry-and-advanced-features&#x2F;geotab-data-connector&#x2F;geotab-data-connector) has a complete breakdown of supported tools and how to connect them. Feel free to reach out if you have any other questions. We are here to help. Have a great day! Eishi FUN

Geotab data connector

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.