Webhooks allow you to receive real-time notifications when certain events occur in your vehicle tracking system. This means you can automate tasks or trigger actions in other systems based on events happening in your tracking system. For example, you could use a webhook to send an email notification to a customer when their vehicle has been delivered or to update a customer's account balance when a delivery has been completed.
To use webhooks for vehicle tracking, you will need to do the following:
Set up a webhook endpoint: This is a URL that your tracking system will send the webhook payload to. You will need to create a server or service that can receive the payload and process it.
Configure the webhook in your tracking system: You will need to specify the events that you want to trigger the webhook, as well as the URL of the webhook endpoint.
Write code to process the webhook payload: When the specified event occurs, the tracking system will send a payload to the webhook endpoint. Your code will need to handle this payload and take any desired actions.
Test the webhook: Once you have set everything up, you will need to test the webhook to make sure it is working as expected. You can do this by manually triggering the event and checking for the desired action to occur.
Webhooks can be a powerful tool for automating tasks and integrating your vehicle tracking system with other systems. With a little setup, you can use webhooks to streamline your workflows and improve efficiency.
Here are some examples of how you could use webhooks with location and time-specific data in a vehicle tracking system:
Send a notification to a customer when their vehicle arrives at a specific location: You could set up a webhook to trigger when the vehicle reaches a certain location (e.g. a warehouse or a delivery destination). The webhook could then send a notification to the customer, letting them know their vehicle has arrived.
Update a customer's account balance when a delivery is completed: You could set up a webhook to trigger when the vehicle reaches the delivery destination and stays there for a certain amount of time (indicating that the delivery has been completed). The webhook could then send a request to update the customer's account balance, reflecting the completed delivery.
Send an alert to a maintenance team when a vehicle goes over a certain speed limit: You could set up a webhook to trigger when a vehicle's speed exceeds a certain threshold (e.g. 80 mph). The webhook could then send an alert to a maintenance team, letting them know that the vehicle may need to be checked for any damage or maintenance issues.
Send a notification to a dispatcher when a vehicle deviates from its expected route: You could set up a webhook to trigger when a vehicle deviates from its expected route by more than a certain distance (e.g. 5 miles). The webhook could then send a notification to a dispatcher, letting them know that the vehicle may be lost or in trouble.
These are just a few examples of how you could use webhooks with location and time-specific data in a vehicle tracking system. Webhooks can be used in many other ways as well, depending on your specific needs and use case.
What data gets sent to a webhook?
When we call your webhook we will send a JSON package containing the vehicle details, driver, event, location, speed and vehicle voltage in the following format:
{"accountId":3,"vehicleRegistration":"7567453451","vehicleId":345934,"vehicleEvent":"DRIVING","driverName":"NW","dateTime":"2023-01-10 11:56:09","location":"M1, London, England, NW7 3","latitude":51.6289668131,"longitude":-0.2625989914,"speedKph":57,"speedMph":35,"geofenceName":null,"congestionZone":null,"externalVoltage":14.5,"internalVoltage":null,"odometer":72185.0}Adding security to your webhook calls
You can optional security headers to your webhook calls via the RAM Tracking setup screen - from the left menu. Adding an auth token will mean that an HTTP header called Auth will be added to the webhook request we send with the value you specify - this allows you to check that the request originated from RAM Tracking.