Skip to content

How-To Guides

Before you begin, ensure you have the following:

  • Trimble ID (TID): All access to the Developer Console is managed through TID. If you do not have a TID, you would need to create one in order to log into the Console.
  • Users that are already part of an IAM account can log in using their existing credentials.
  • Users that are not part of an IAM account can sign up and an account will be created automatically based on the information on your TID account upon sign-up.
  • Access to the Developer Console does not require any product licensing or entitlement.
  • Applications belong to teams, which belong to IAM accounts.
  • You must review and accept the Terms and Conditions during the onboarding process.

A Team in the Trimble Developer Console is a shared workspace for managing applications and credentials. Each Trimble account supports one team only, and direct team creation is restricted to Primary and Secondary Account Owners.

  1. Select the account from the Account Name dropdown.
  2. Select Create Team.
  3. Enter a Team Name and Team Description, then select Create Team.
  4. You will automatically become the Team Admin and can add members under Team > Team Members.
  • If no team exists: Selecting the account displays a modal listing active Primary and Secondary Account Owners (name, email with copy-to-clipboard, and role label) so you can contact them to create the team.
  • If a team exists: Select Request to Join. The request is sent to the Team Admin for review.

If an account lacks active Primary or Secondary Account Owners, Create Team is disabled and an error modal appears with a Learn more link explaining how to assign an active owner.

Once the team gets created, the creator of the team becomes a “Team Admin” and can add additional members to the team by clicking the “Add member” button under Team > Team Members tab.

A team member can be added in the team and granted any of the roles described below:

Understanding roles is critical for managing your application’s lifecycle:

RoleCapabilities
AdminInvite team members, enable product sandboxes, edit all applications in a team and authorize applications on an account level.
DeveloperA developer may create, delete, and edit their own applications, including client secret rotation and callback URL management. They may not invite or delete team members or create new sandbox environments.
GuestGuest users have the same core capabilities as developers but cannot create teams, publish apps to the Marketplace, or access Sandboxes for testing. To enable these capabilities, they must contact their Account Admin to be added to the account.

Only an Admin can invite additional developers to a Team.

To invite users to a team, admins need to navigate to Team Members > Add Member > Enter email address > Select the role in the team > Add member

The invited user receives an email with a link to the Console, where they can accept or decline the invitation.

Admins can also add users who are not part of the IAM account into a team and grant them either an Admin or a Developer role in the team. But in that case they are considered as “Guest Users”. Guest users will not have the ability to do a few things in the Developer Console and should reach out to the Account Admin to get added to the Account.

Guest Users cannot:

  1. Create new teams under the IAM account
  2. Publish apps to Marketplace
  3. Cannot access Sandboxes for testing

Developers can join an existing team in their account by selecting Request to Join after logging in to the Console.

If the developer is associated with more than one account, they must first select the account that contains the team they want to join, then select Request to Join.

If a developer has already created or joined a team and wants to create or join additional teams under other accounts they are associated with, they can navigate to Team > Browse all teams > Add team.

After selecting a team and submitting a join request, a Team Admin must approve it before you can become a member.

Applications in the Trimble Developer Console act as the secure container for your API credentials and govern how your code interacts with Trimble products. By creating an app, you generate the unique identity your integration needs to authenticate and access data.

Before you begin:

  • Create a Team: Ensure you have created or joined a team workspace, as all applications must belong to a collaborative team.
  • Identify your API: Know which Trimble product (e.g., ProjectSight or Trimble Connect) you intend to integrate with.

Navigate to your team’s Applications tab and click Create App to launch the setup wizard.

Provide a unique Name and a brief Description for your application. These details help to identify the purpose of the integration during the authorization process.

An API Product is a subscription that allows your application to securely access data and services from a specific Trimble product (such as ProjectSight or Trimble Connect). It enables your app to authenticate and interact with Trimble APIs to perform tasks and integrations.

Choose the specific Trimble product you wish to integrate with from the provided list.

Select the application type that matches your integration’s architecture:

  • End-User App: For web or mobile apps where a user signs in (uses Authorization Code Grant).
  • Server-to-Server App: For back-end services or scripts running without user interaction (uses Client Credentials Grant). These type of applications cannot be published to Trimble Marketplace by partner developers.
  • Extension App: Specifically for embedding UI extensions within products like Trimble Connect.

Each API Product may support different application types. Review the product-specific documentation to understand which application types are available and choose the right option for your integration.

Once your application gets created, navigate to the Credentials & Grant Type tab in the application overview. Here you will find your:

  • Client ID: Your app’s public identifier.
  • Client Secret: A private key used to authenticate your API calls.

As a developer, you can manually rotate the client secret, which provides a 24-hour grace period that keeps the legacy secret valid and usable for up to 24 hours after rotation, or opt to instantly revoke a leaked legacy secret without any grace period.

If an application is no longer needed, you can remove it to keep your workspace organized. Deleting an application permanently retires its credentials and immediately stops its ability to receive successful responses from Trimble APIs.

You can delete an application in two ways within the Developer Console.

  • From the Application List: Navigate to Team > Applications, locate your app in the list, and select Delete App from the three-dot menu (…) on the right.
  • From the App Details Page: Select your application from the list to open the App Details page, then click the Delete Application button.

Important Restrictions

To maintain the integrity of the ecosystem, certain applications are protected from deletion. You cannot delete an application from the Developer Console if it has entered the Marketplace lifecycle.

Applications with the following statuses cannot be deleted:

  • Pushed: The app has been submitted for Marketplace consideration.
  • In Review: The Trimble Marketplace team is currently auditing the application.
  • Published: The app is live and available on the Marketplace.

If not yet familiar with Trimble ID authentication, view our guide on how to perform an initial API transaction. It provides direction on interactive user login, getting a token, and calling an endpoint with both Trimble ID and Trimble Connect API examples included (which can be applied to other API products in the Developer Console, too).

Applications created within the Trimble Developer Console must be authorized before they can interact with account data or services.

Note: This authorization workflow applies only to applications developed and owned by the same account where they will be used. Applications developed by external or third-party accounts follow a separate authorization process.

The authorization action available to you depends on your assigned role for the account:

  • Primary & Secondary Account Owners: Can authorize applications directly within the Developer Console.
  • Non-Account Owners / Developers: Must request authorization from the account’s Primary and Secondary Account Owners.

Direct Application Authorization (Account Owners)

Section titled “Direct Application Authorization (Account Owners)”

Primary and Secondary Account Owners can authorize applications without leaving the Developer Console:

  1. Navigate to Applications and select the target application to open the Application Overview page.
  2. Select Authorize for Production.
  3. Review the details in the confirmation modal.
  4. Select Authorize for Production to confirm.
  5. Once authorized, the status updates immediately on the Application Overview page, and also appears under “Enabled” tab in Admin Console.

Requesting Application Authorization (Non-Owners)

Section titled “Requesting Application Authorization (Non-Owners)”

Users without direct authorization permissions can submit a request to the Account Owners:

  1. Navigate to the Application Overview page and select Request Authorization.
  2. An email notification will automatically be sent to all active Primary and Secondary Account Owners for review.
  3. A success message will confirm that your request has been submitted.

Account Owner Notification & Review Workflow

Section titled “Account Owner Notification & Review Workflow”

When an authorization request is submitted by a developer:

  1. All Primary and Secondary Account Owners receive an email notification containing application details.
  2. Selecting Authorize from the notification directs the owner directly to the authorization flow in the Admin Console.
  3. Owners can choose to either Authorize that application or take no action on the request.

Applications can also be authorized from the Admin Console for applications created by the same account as well as by other third-party developer accounts by using the application ID. Details can be found Admin Console Documentation.

Note: After the application has been authorized in Admin Console, there may be additional actions that would be needed in the respective Product application. For more details, please refer to the respective product’s Help Documentation.

Listing your application on the Trimble Marketplace allows you to distribute your application across the Trimble ecosystem. Publishing is handled on a per-application basis and involves two main steps: Partner Verification (for your account) and Application Publishing.Learn more about becoming a Technology Partner.

In order to publish to the Trimble Marketplace, you first must be a Trimble Technology Partner.

Before listing an application, ensure your setup meets the following requirements:

  • Technology Partner Account: The application must be created under an account registered as a Trimble Technology Partner.
  • Account Permissions: Guest users cannot push applications. You must be added to a specific company account by the Account Owner in order to be able to Push apps to the Marketplace.
  • Eligible Application Types: Only End-User Apps (including Extension Apps) can be published to the Marketplace. Server-to-Server Apps are for internal background processes and are ineligible.

Complete Partner Onboarding

If your account is not yet registered as a Marketplace partner, you must complete the partner verification form before pushing applications:

  1. Log in to the Developer Console and navigate to the team that owns the application you want to publish.
  2. Navigate to the Marketplace tab under that team.
  3. If your account is not verified, you will be directed to the Marketplace Partner Program registration form.
  4. Complete the required details in the form:
    • Individual Account: Select Individual, then provide your first and last name, email, country or region, phone number, and address.
    • Business Account: Select Business, then provide your Trimble Account ID, email, country or region, phone number, address, company name, company size, special tax treatment status, and Tax ID (if applicable).
  5. Click Submit for Review.

Note: Submitting this form generates a Lead for the Marketplace team to audit and verify your individual or business account. Once verified, a Partner Verified status badge will display under your account settings.

Push Your Application to Marketplace

Once your account is verified as a Marketplace enabled Technology Partner, you can submit individual applications:

  1. Navigate to Applications and select the specific app you want to publish.
  2. Select the Marketplace tab from the left sidebar of your application overview page.
  3. Click Push to Marketplace.
  4. The application status updates to Pushed.

Important Restriction: Once an application is Pushed, it enters the Marketplace lifecycle and cannot be deleted from the Developer Console.

Manage Listing in Marketplace

After pushing your application, a skeleton product listing is created in the Marketplace backend. (Note: You will only see this option if you have a valid Trimble Marketplace credential.)

  1. On the app’s Marketplace tab in the Developer Console, click Manage Listing.
  2. You will be redirected to the Marketplace Portal. Sign in with your credentials.
  3. Fill out the required marketing and listing assets.
  4. Click Submit for Review.

Review and Publication Workflow

StatusDescription
PushedThe app skeleton has been generated and sent to the Marketplace portal.
In ReviewThe Marketplace team audits your listing content, security scopes, and compliance.
PublishedUpon approval, your application goes live on the Trimble Marketplace storefront, allowing end-users to discover and authorize your integration.

Refer to the Marketplace Documentation: https://developer.trimble.com/docs/marketplace for more information.

In order to perform certain actions on the platform and in the Developer Console, a user will need owner-level account access. View the account owner access portion of our Trimble Developer Support page for help if needed.