New API: CheckCompatibility
We've added a new unary endpoint called CheckCompatibility. It allows users to check if their vehicles can connect to the Native Connect platform and what data variants they will receive (e.g. latitude/longitude, speed, odometer, fuel/charge). Available data variants are dependent on the specified use case.
In the request, simply provide:
- the VIN you wish to check,
- the region the vehicle is in,
- and the use case the vehicle will be used for (B2B and B2C).
If the VIN is compatible, the response will provide the list of supported data variants, and information needed to add the vehicle to Native Connect through the InitiateVehicleSignUp or BatchVehicleSignUp endpoints.
If the VIN is incompatible, the response will return an incompatibility message.
What can I use this endpoint for?
This endpoint allows you to check if your vehicle is compatible with Native Connect. Checking vehicle compatibility can help understand if there will be connection issues. Please note that this endpoint will tell you if your vehicle is compatible; there may be other connection issues like firmware versions or specific user settings that may prevent a compatible vehicle from connecting to Native Connect. If this is the case, please contact our team.
What is the difference between B2B and B2C use cases?
B2B use cases are for fleet management, where you or your company personally own the vehicle. This means you receive more in-depth data.
B2C use cases include insurance, roadside assistance, energy grid and Road User Charging uses, where you do not personally own the vehicle, but will be integrating customer vehicle data for a seamless and better service.
What regions can I request?
The regions you can request are:
Please note that not all vehicle brands will be supported in all these regions.
How do I get a vehicle VIN?
You should already have the vehicle VIN before checking the compatibility and signing it up to Native Connect.