Issue No. 23 | August 2026 

Welcome! This month’s edition highlights our unified Model Context Protocol (MCP) strategy for scaling Agentic AI, the release of Admin Console & My Products v5.3 featuring a newly redesigned Home page, and the U.S. launch of Trimble Financials Go. Inside, you will also find crucial updates regarding the Trimble ID redesign and upcoming Identity and Access Management (IAM) migrations, alongside comprehensive release notes detailing the latest security, scalability, and developer experience enhancements across Trimble Identity, API Cloud, and File Service.

🛠️ MCP Strategy and Alignment

As Agentic AI applications scale across Trimble, seamlessly connecting LLMs to secure data sources and tools is critical. To make this happen efficiently, the Agentic and API Cloud teams are joining forces on a unified, enterprise-grade Model Context Protocol (MCP) strategy and standard.

🚀 Admin Console & My Products v5.3 

We’ve made another release of the Admin Console and My Products, v5.3! This release includes one big feature: A new Home page! This home page displays different information based on the customer’s products and the user’s role:

  • Small Ecommerce customers with one product can manage their subscription (turn off auto-renewal, add seats, remove seats) from the Home page without navigating elsewhere.
  • Sales rep customers will see a concise dashboard showing the products they have the most seats of, quick links to manage users and licenses, and recent order history.

🚀 Trimble Financials Launches in U.S.

We are thrilled to share some great news: Trimble Financials Go has launched for ecommerce and the SMB pilot program sellers for the QuickStart packages on July 20th!

🚨 Important Reminder: Trimble Connect Internal Webinar Recordings

Please note that internal webinar recordings for Trimble Connect are strictly for internal use and must not be shared externally with clients, prospects, or external partners.

Dealers may be referred to the Trimble Learn Recording Channel

🇲🇽 Mexican Peso (MXN): New Currency  Available on eCommerce

We are excited to share that our eCommerce platform now supports the Mexican Peso (MXN) for our customers in Mexico.This update implements currency localization within the checkout flow, allowing users to view product pricing and complete purchases directly in their local currency. We appreciate your ongoing partnership as we continue to enhance the eCommerce platform.

Trimble Platform on Charlie

Join our Community on Charlie for the latest Platform news.

📅 reminders

[Action Required] Trimble ID: Redesign - User Authentication Refresh

The Trimble ID (TID) team is launching the TID Redesign Initiative – a comprehensive refresh of the user interface designed to provide a smarter, faster, and more intuitive authentication experience based on the principle of being “secure by default”.

Staging - June 16, 2026

Production - Q3 2026

[Action Required] Identity and Access Management (IAM): Reference Data Endpoint Migration (Countries, Languages, Timezones)

The countries, language, and timezone data currently sourced from the Tpaas account will be decommissioned. From now on, this data will be provided by IAM. Accessing this endpoint requires no specific subscription; any user with a valid TID token can obtain the details. Refer to the documentation tab for instructions on using these endpoints.

The reference data is moving from the legacy public storage S3 bucket (https://s3-us-west-2.amazonaws.com/profilex-validator/...) to the IAM API with a TID token.

If your applications or services consume the legacy public reference-data URLs, update them to use the new IAM API endpoints, ensuring each request includes a valid TID token.

Legacy Endpoint Expiration Date (PROD & STAGE): September 31, 2026

IAM: Geo-Isolation Strategy

We are sending this notification as a follow-up to our earlier communication from March 2026. Our geo-isolation strategy for the Identity and Access Management (IAM) product is currently being refined. We are committed to providing you with sufficient lead time once the strategy is finalized and implemented, and we will share further updates as they become available.

📅 UPCOMING EVENTS

API Cloud: mTLS Certification Expiration

API providers utilizing mutual TLS (mTLS) are required to integrate their trust stores with the new Root CA. This update must be completed for API proxies in the Pre-Production environments prior to September 1, 2026, and for Production environments before September 15, 2026. Failure to implement these updates within the specified timeframes will result in API client authentication failures.

Pre-Production: September 1, 2026

Production: September 15, 2026

Profiles API: Migration of Users Read/Search Admin Access from Profiles to IAM

As the Profiles application is targeted for an EoL in the near future, we have identified the list of integrating applications which possess Users Read/Search admin access in the Profiles system. As an initial step, we request all these integrating applications to migrate from utilising Profiles to IAM APIs.

🚨 DISASTER RECOVERY

Trimble File Service: Disaster Recovery Drill in Staging(AWS)

Trimble File Service will conduct a Disaster Recovery drill in the Staging EU region(AWS and Azure) on August 18th, 2026. This drill may result in intermittent availability for all integrators with applications in our Staging environment.

Staging - August 18, between 3:30 AM and 8:30 AM UTC

🚀 RELEASE NOTES

🛡️ Trimble Identity

This past month, our platform teams focused on streamlining the authentication experience, expanding our OAuth capabilities, and reinforcing our core security infrastructure. Here are the key highlights to keep on your radar:

  • Elevated User & Developer Experience: We’ve optimized our onboarding flow by reducing sign-up latency and introduced a newly redesigned login error experience for TID-v2. Additionally, auth screens now feature full Dark Mode support for application logos, alongside broad internationalization (i18n) updates. For our builders, we've smoothed out account creation and session association in the Developer Console.
  • Advanced Authorization & Account Management: API product scopes are now dynamically resolved and attached to OAuth endpoints. We've also introduced optional support for subject-delegation tokens in the on-behalf-of (OBO) flow. On the user side, we've added a self-service recovery path to cancel pending account deletions and implemented smarter default-account fallback logic.
  • Security & Infrastructure Enhancements: We’ve rolled out strict TLS enforcement across all regions and successfully completed our annual mTLS certificate rotations. Under the hood, OpenID configuration discovery has been cleaned up, and platform logging pipelines have been optimized.

☁️ API Cloud

This past month, the API Cloud team made significant strides in fortifying our security posture, scaling our core infrastructure, and delivering a much smoother experience for developers navigating our console. Here is a summary of the key improvements:

  • Next-Gen Hosting & Live Sync: We’ve rolled out core hosting infrastructure (currently in staging) specifically designed for platform MCP servers, featuring automated provisioning directly from GitHub with real-time status tracking. Additionally, we’ve replaced mocked endpoints with real-time live synchronization for IAM products and application ownership mapping.
  • Enterprise Security & Governance: Security remains our top priority. We achieved FIPS compliance for our Application Load Balancers (ALB) to support FedRAMP standards, and implemented strict DPoP header validations for access tokens. We also introduced comprehensive Cloud Console audit logging and proactively removed third-party tools (like Gainsight) that did not meet our strict internal security standards.
  • Developer Console Redesign: We’ve completely revamped the Developer Console’s team onboarding with a unified "Add Team" workflow. The developer experience is further improved by persistent Dark Mode, cross-browser UI fixes (specifically for Firefox), stricter URL validation, and a much smoother user-invitation flow for various account types.
  • Resiliency & Core Scalability: Under the hood, we completed major refactoring of the Gateway Provisioner for architectural stability. Crucially, we enhanced our system to allow seamless scaling of API Management (APIM) units—even during partial or full APIM outages.

📁 File Service

As we continue to scale the Trimble Platform globally, our recent File Service releases (v2.22.0 and v2.23.0) focused on unlocking greater scalability, hardening our security posture, and streamlining compliance for our enterprise and government partners.

Here are the key capability highlights from our latest rollout:

  • Unlimited Support Files: We’ve officially removed the hard limit of 50 support files per main file in the V2 API. To guarantee smooth performance with these higher data volumes, we’ve introduced asynchronous job tracking to safely handle large-scale file moves and restores without hitting transaction limits.
  • Advanced Security & Authorization: We’ve rolled out Delegated Authorization token support across our APIs and processing engines, enabling much more flexible, delegated access control for API clients. We've also fortified our DPoP token validation to ensure tokens are strictly bound to their intended request URIs.
  • GovCloud & FedRAMP Readiness: To better support our highly regulated environments, we’ve introduced streamlined, AWS-only packaging and deployment pipelines specifically optimized for GovCloud rollouts.
  • Performance & Developer Experience: We've implemented region-aware endpoint routing to eliminate sequential probing and speed up cross-region API calls. Additionally, we've improved API payload consistency and replaced obscure database errors with clear, actionable validation messages for duplicate customId conflicts.

Platform Support

Service Requests

Integrators with questions regarding their Platform adoption or retention (e.g., related to compliance, configuration, data, training, or reporting) should submit a generic request.

Incident Reporting

Integrators should report incidents when they observe a degradation or major outage of a Platform Service that affects their business operations. If the Impacted service is not listed, then please contact the Impacted Services point of contact(s) directly.



Need to join the mailing list for this newsletter or know someone who does? Let us know by filling out this very short form: