October 2025

High Mobility platform updates on October 2025

Changed: Tesla Clearance Reject Reason

When a vehicle is not found in the customer’s granted consent, the API will now return “consent assignment missing” instead of “invalid VIN” as the reject reason. This provides clearer feedback about the consent state.

Changed: Volkswagen Brand Clearance Activation

For Volkswagen-brand vehicles, clearance now activates only after data delivery is received from the vehicle. the Volkswagen clearance lifecycle is update to refelect the new changes.

• While a vehicle is pending due to missing data, the clearance status will show no data received .

• If no data is received for 10 consecutive days, the clearance will automatically change to rejected with reason activation timeout: no data .

Added: Volkswagen Brand Clearance Rejeact Reason

We have new reject reasons for VW brands:

• software version incompatible

• primary user enrolled

• mod incompatible

• activation timeout: no data

Deprecated: End-of-Support for Legacy APIs & SDKs

Over the past few years, we’ve introduced many new integrations and APIs to give you more ways to connect to your fleet data. As part of this progress, some older APIs and tools are being retired. The table below outlines the end-of-support date for the affected endpoints and SDKs, along with their recommended replacements. While most of our customers and partners have already migrated, we encourage you to review the table below and verify whether any action is needed on your side. Our team will also reach out directly to affected accounts where necessary. * Rest-API V5, replaced by Vehicle Data API Impacted API: https://rest-api.high-mobility.com/v5 (or any older version) New API: https://api.high-mobility.com/v1/vehicle-data/autoapi-13/:vin End-of-Support: October 31st, 2025 * Java Fleet SDK, replaced by Vehicle Data API and Fleet Clearance API Impacted SDK: https://github.com/highmobility/hmkit-fleet New APIs: https://api.high-mobility.com/v1/vehicle-data/autoapi-13/:vin https://api.high-mobility.com//v1/fleets/vehicles End-of-Support: October 31st, 2025 * GraphQL API, replaced by Vehicle Data API Impacted API: https://graphql-api.high-mobility.com/ New API: https://api.high-mobility.com/v1/vehicle-data/autoapi-13/:vin End-of-Support: October 31st, 2025 * Service Service Account Token API, replaced by OAuth API with client_credentials Impacted API: https://api.high-mobility.com/v1/auth_tokens New API: https://api.high-mobility.com/v1/access_tokens End-of-Support: October 31st, 2025 * hmkit-node SDK, replaced by Vehicle Data API Impacted SDK: https://github.com/highmobility/hmkit-node New API: https://api.high-mobility.com/v1/vehicle-data/autoapi-13/:vin End-of-Support: October 31st, 2025 * Android SDK, no replacement Impacted SDK: https://github.com/highmobility/hmkit-android End-of-Support: October 31st, 2025 * Python SDK, no replacement Impacted SDK: https://github.com/highmobility/hmkit-python End-of-Support: October 31st, 2025 * iOS SDK, no replacement Impacted SDK: hm-ios-sdk End-of-Support: October 31st, 2025 What do you need to do? ‍If you are using any of the APIs or SDKs listed above, please migrate to the recommended replacements before October 31, 2025 to ensure uninterrupted service. ‍We’re here to help ‍If you have any questions or would like support with your migration, please contact our team. We’re happy to discuss your specific needs and guide you through the process