Skip to content

OEM Credentials⚓︎


OEM Credentials are only required if you want to add NIU, Segway or Mercedes-Benz vehicles. When adding CloudBoxx vehicles, you do not need to provide credentials. INVERS associates your purchased CloudBoxxes with your fleet automatically.

What are OEM credentials?⚓︎

The INVERS OneAPI does not only support our own CloudBoxx telematics unit, but also several telematics unit models from other vendors. Those are mostly telematics units that have already been installed into the vehicle by the vehicle’s manufacturer (the OEM).

In order to access those vehicles through the INVERS platform, you will need to add OEM credentials to your OneAPI fleet. You will typically receive those credentials from the corresponding OEM if you purchase vehicles which are already equipped with an OEM telematics unit. Separate contracts are oftentimes necessary between you and the OEM.

Different OEMs require different forms of authentication, and therefore OEM credentials vary from one manufacturer to the other. One set of OEM credentials is typically shared by a group of vehicles (e.g., all vehicles you purchased from that particular OEM). We call these kind of credentials shared credentials. You only need to associate these credentials once with your INVERS OneAPI fleet. The OEM credentials are then safely stored and can be used for all vehicles that are associated with this set of credentials. You can subsequently add these vehicles to your fleet.


In some cases each individual telematics unit requires its own password or set of credentials. This is mostly the case if a direct connection to the telematics unit via TCP is used instead of a cloud solution or OEM API. You will need to provide individual credentials for each vehicle when adding such a vehicle to your fleet. In such a case, you don’t need to provide the aforementioned shared credentials beforehand.

How to add OEM credentials⚓︎

Our FleetControl UI allows you to store and manage shared credentials. Simply navigate to Administration > OEM Credentials. We recommend to use this way over using the OEM Credentials API mentioned below, as it is only a one-time task to store your OEM credentials. When creating new credentials, you should specify a name. This name has to be unique within your fleet and makes it easier for you to reference the credentials later on, for example when adding vehicles to your fleet that require them.

You can store multiple credentials for the same third-party API, e.g., Mercedes-Benz, within your fleet. By doing so, you can use vehicles that require separate credentials for the same third-party API in one single OneAPI fleet.

OEM Credentials API

API Reference

API Changelog

Alternatively, credentials can be added using the POST endpoint of the OEM Credentials API (see box on the right hand side). A unique identifier will be generated for all credentials. If you are adding vehicles to your fleet using the Vehicle Lifecycle API, this ID is required to tell the INVERS OneAPI which credentials to use in order to access the vehicle via the OEM / third-party API.

How to update or delete existing OEM credentials⚓︎

The client_secret can be updated using the PATCH endpoint of this API (see API specification). Use the DELETE endpoint in order to delete a set of credentials (identified by their identifier). You can only delete credentials if they are no longer used by any of the vehicles in your fleet.


You can only update the client_secret or password. Credentials with a different client_id or username are considered entirely new. Add them as described above in how to add new credentials.


The following examples shows how to add new OEM credentials. Follow instructions to get an access token first in order to retrieve a valid access token for the INVERS OneAPI.

curl -X POST \
    '❰brand❱/credentials' \ # (1)!
    -H 'Authorization: Bearer ❰access_token❱' \ # (2)!
    -H 'Content-Type: application/json' \
    -d '{
          "name": "Mercedes-Benz fleet Berlin",
          "client_id": "client1",
          "client_secret": "supersecret"
        }' # (3)!
  1. Insert the telematics brand for which you want to store credentials.
  2. Don’t forget to fill in your access token.
  3. Please provide your credentials for the third-party API and choose a name.

    You can also provide a name to easily reference the credentials later.

If the request has been successful, a JSON object is returned along with HTTP status code 201.

Here’s an example of what the response might look like:

  "id": "01F62857KMPG2NE2GK1W2N3QYS",
  "name": "Mercedes-Benz fleet Berlin",
  "client_id": "client1"