Change to RealtimeRawPointByVins
We’ve changed the streaming RealtimeRawPointByVins API, renaming it to RealtimeStitchedPointsByVins .
The new RealtimeStitchedPointsByVins endpoint has the same request and response structure as the previous RealtimeRawPointByVins. It allows users to receive real-time stitched data points for vehicles in their workspace. So, if vehicles in your workspace are travelling, this API will provide the vehicle’s live location and other collected metadata, similar to the GetLivePoint unary endpoint.
To request this endpoint you will need to:
- Provide the vehicle VINs you want realtime stitched points for.
- Specify the maximum latency (meaning the highest delay) that can be tolerated for this data stream. This will need to be in minutes.
In the response you will see the timestamp, position (including bearing, speed, latitude and longitude), odometer, vehicle make and model, and trip ID of each point. You will also see when the point was ingested by Native Connect, and extra metadata like fuel or charge level, gyroscopic data, and acceleration.
New API: RawPointsByVins
The new streaming endpoint RawPointsByVins, provides even rawer vehicle data than the new RealtimeStitchedPointsByVins endpoint.
This means the data points are passed directly to you from the provider before being ingested by Native Connect. Please note, because of this you may receive complete data packets or partially-filled packets, and real-time data along with older data. There is no completeness or realtime guarantee with this endpoint.
To request this endpoint you will need to:
- Input the vehicle VINs you want realtime raw points for.
- Create a unique identifier or name for your data stream. This helps us to keep track of the which packets have already been sent through the stream and to avoid duplication if you need to retry the stream. Once you’ve provided the unique name, reuse the same name for every consecutive stream retry.
In the response you will see the timestamp, position (including bearing, speed, latitude and longitude), odometer, vehicle make and model, and trip ID of each point. You may also receive extra metadata like fuel or charge level, gyroscopic data, and acceleration.
What can I use these endpoints for?
Both these endpoints allow you to see where and when vehicles in your fleet are moving. This helps know where all your fleet vehicles are, and receive extra metadata during trips. The difference is the RawPointsByVins is the rawest form of this data, and isn’t necessarily real-time, meaning you receive the points from the provider before we filter or trip-stitch them.
How do I get a vehicle VIN?
You should already have the vehicle VIN. If you want to see all the vehicles in your fleet you can use the GetVehicles endpoint.