OEM Integration: CAT

Requesting CAT 2.0 API Credentials:

Step 1. Coordinate with your CAT dealer

Only your dealer can enter the following sites and fill the form.

Pro Tip! Have your CAT UCID handy!

IMPORTANT: Make sure you instruct the dealer that you are requesting the ISO 2.0 API credentials NOT the Visionlink API.

Have your dealer fill out the Basic Daily and ISO 15143-3 (AEMP 2.0) Subscription Form


Step 2. You should receive an email from CAT Digital Support providing your API credentials. 

It should be a client and a secret in an attached .txt file:

  • client credentials (Ex: fleet_mgmt_cust_XXXXXXXXXX_cc_client)
  • client secret (64-characters) (Ex: lvUyxWvnr53siEuR3GCUw6NxpcVB0XGTe9TViBZ66gXulecUYdqlkaR65Z9UuYtz)

Enabling the Integration within Tenna:

Step 1. A Power User must be logged in to establish the integration.

Note: If you already have Tenna Power User credentials, move on to the next step.

For help identifying a Tenna Power User, contact Tenna Customer Success at (833) 50-TENNA.

To add a new Power User or modify an existing user, view How to Create a User and Contact.

Step 2. Click on Settings in the top Global Navigation.

Step 3. Click on the Integrations tab.

Step 4. Select OEM from the Integrations landing page.

Step 5. Enter the ISO API credentials provided and select Sync.

Step 7. If this is your first integration setup, a Disclaimer acceptance window will open.

Please review and when finished, click Accept.

Note: After a Power User accepts this on the company's behalf, the disclaimer will not be displayed again.

Step 8. If the integration connects successfully, Connection Online will be shown on the screen.

Step 9. Next, you will need to manually sync the OEM's asset to a Tenna asset by selecting Fix Issues.

Step 10. Selecting the Manage button will allow you to view all synced assets and remove an asset's association to the OEM.


Support: For questions, reach out to the Tenna Integrations Department [email protected].

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.