Onboarding

In-fleeting Requirements

For the VW brands, a document needs to be signed by the Fleet owner/operator, which will apply to the entire Fleet. This step is mandatory for all third parties/solution providers as it’s a legal requirement.

The HM Biz Dev Team will provide you with a custom Boldsign link that you can provide to your Fleet customers in order to digitally collect thee signature.

This will be considered as a one-time consent on their whole Fleet of VW Group vehicles (including the brands Audi, Skoda, Volkswagen, SEAT, Cupra)

Privacy settings

For Audi, Skoda, Volkswagen, SEAT and Cupra, vehicles could have the Privacy settings switched on.

This setting will need to be changed in the vehicle, and you can also take the opportunity to check if the latest Software updates need to be installed in the vehicle.

• Note: Once the vehicle is successfully activated, the Driver can no longer change the Privacy settings in the vehicle. This ensures data transmission while the vehicle is connected.

You can provide the following instructions to your Fleet customers or Fleet operators in order for the Privacy settings to be changed in anticipation of the onboarding and activation of the vehicles.

Links to Instructions for manual deactivation of Privacy Mode:

ℹ️ Volkswagen Privacy Setting EN

ℹ️ Audi Privacy SettingVW_Privacy_Setting_EN.pdf EN

ℹ️ Skoda Privacy Setting EN

ℹ️ Seat & Cupra Privacy Setting EN

ℹ️ Volkswagen Commercial Vehicles Privacy Setting EN

*MOD4 vehicles and Audi vehicles are not able to provide live location data

Fleet Clearance

In order to onboard VW Group vehicles, you will need to additionally specify the name of the Fleet customer as a "tag" vw-group-customer-name in our Fleet Clearance API.

Please consult our documentation:

ℹ️ Fleet clearance tutorial - Using tags

This tag should correspond to the Fleet operator business name, which we associate with the specific VIN activation.

The following shows an example of how vehicle clearance objects are passed in with a tag set:

curl -X POST https://api.high-mobility.com/v1/fleets/vehicles \
--data '
{
  "vehicles": [
    {
      "vin": "VIN01234567890123",
      "brand": "audi",
      "tags": {
        "vw-group-customer-name": "Car Operations Ltd."
      }
    }
  ]
}'

If you are a direct Fleet Operator or always activate VINs for the same Fleet Operator, our support team can configure a default Business name for a specific data project.

This removes the need to include the vw-group-customer-name tag in the Fleet Clearance API.

Please let us know during onboarding or contact our support team at [e-mail].

OEM Workflows

Privacy settings during a clearance

If the privacy settings of a VW Group vehicle are enabled during the activation attempt, the vehicle will stay in the pending state while we keep retrying the activation. If the settings have not been disabled within 5 days, the activation attempt is rejected.

When privacy settings are blocking the activation, you can detect it in the reason field of the clearance object:

{
  "vin": "VIN0TESTVIN000000",
   "status": "pending",
   "brand": "volkswagen",
   "changelog": [
     {
       "timestamp": "2025-01-22T10:42:14",
       "status": "pending",
       "reason": "privacy mode is enabled"
     }
    ]
}

EV vehicles with an active primary user

Currently, the VW API does not allow vehicles that are activated via their B2C app to be enrolled into a fleet. If this occurs, the vehicle will be rejected with the following reason:

{
  "vin": "VIN0TESTVIN000000",
   "status": "rejected",
   "brand": "volkswagen",
   "changelog": [
     {
       "timestamp": "2025-01-22T10:42:14",
       "status": "rejected",
       "reason": "primary user enrolled"
     }
    ]
}

To resolve this issue, please perform the factory reset using the infotainment system: (Go to Home > Vehicle Settings/Setup > Reset to default settings.)

This limitation is expected to be resolved in Q1 2026.

Vehicle with no data

If you attempt to activate a vehicle and the vehicle doesn't transmit data, the vehicle stays in pending state. In the API you see with this status

{
  "vin": "VIN0TESTVIN000000",
   "status": "pending",
   "brand": "audi",
   "changelog": [
     {
       "timestamp": "2025-01-22T10:42:14",
       "status": "pending",
       "reason": "no data received"
     }
    ]
}

If after 10 days there is no data transmitted, the vehicle gets rejected:

{
  "vin": "VIN0TESTVIN000000",
   "status": "pending",
   "brand": "audi",
   "changelog": [
    {
       "timestamp": "2025-01-22T10:42:14",
       "status": "pending",
       "reason": "no data received"
     },   
     {
       "timestamp": "2025-02-12T10:42:14",
       "status": "rejected",
       "reason": "activation timeout: no data"
     }
    ]
}

More Information

If you have any questions, please contact us on Slack or send us an email.