We’re excited to announce that Accident Detection, Driver Pair message, and Driver Unpair message webhook events have now been added to the webhook documentation on the Azuga Developer Portal! These updates expand our event catalog and strengthen integration capabilities for partners and customers.

📡 Published Events

✅ Accident Detection ✅ Driver Pair Message ✅ Driver Unpair Message

📘 Each event includes detailed documentation covering:

🔹 Webhook Categorisation – Classification based on module and functionality
🔹 Event Name – Standardized event type
🔹 Event Description – Clear explanation of the use case and purpose
🔹 Subscription Package – If applicable
🔹 Trigger Condition – Exact conditions under which the event is triggered
🔹 Payload – Complete JSON structure sent via webhook
🔹 Payload Reference – Field-by-field explanation and examples` 

📄Event Summaries

1️⃣Accident Detection:

The Accident Detection webhook is triggered when the device detects a potential or confirmed collision, enabling fleets to react quickly to safety incidents with real-time crash data.

For more information refer Accident Detection

2️⃣ Driver Pair Message

The Driver Pair webhook notifies when a driver successfully pairs with a vehicle using an input method such as iButton, RFID, or mobile authentication. This helps maintain accurate driver-to-vehicle assignment records.

For more information refer Driver Pair Message

3️⃣ Driver Unpair Message

The Driver Unpair webhook triggers when a paired driver disconnects from a vehicle—either automatically at trip end or when manually unpaired. This keeps integrated systems up to date with driver assignment changes.

For more information refer Driver Unpair Message

More webhook events will continue to be added to enhance automation, safety monitoring, and integration flexibility.

Updated Base Url for v4 apis.
Refer here

🔍 What’s New?

Health Report capabilities:

1. Fetch Health Report Data
2. Fetch Scheduled Health Report
3. Schedule Health Report
4. Update a Scheduled Health Report
5. Delete a Scheduled Health Report
6. Validate Report Name for Scheduled Reports

🔗 Explore the Docs: SafetyCam Health Report – API Reference

We’re excited to share that additional webhook events have been added to our Phase 2 documentation Azuga Developer Portal! These updates expand event coverage and enhance the clarity and utility of our integration tools.

📡 Published Events:

✅ Fuel Events (Fuel Increase, Fuel Decrease, Fuel Level Remaining %, and Low Fuel)
✅ Vehicle Events (Vehicle Creation, Vehicle Updation, and Vehicle Deletion)
✅ Oil Life Remaining (%)
✅ GPS Message
✅ Hard Acceleration
✅ Hard Braking
✅ Hardcore Braking
✅ Over Speeding (Overspeeding and Overspeeding Ended)
✅ Seat Belt
✅ Trip Events (Trip Start and Trip End)

📘 Each event includes comprehensive documentation:

  🔹 Webhook Categorisation  - Classification of Webhook Events Based on Module Features
  🔹 Event Name
  🔹 Event Description
  🔹 Subscription Package if Required
  🔹 Trigger Condition – When and why the event triggers
  🔹 Payload – Full event payload structure
  🔹 Payload Reference – Field-level descriptions and examples

More events will be added in the future to expand integration capabilities.

🚀 New in Our Modern V4 API: Vehicle & Users Modules

Introducing two powerful additions to the V4 API platform:

✅ Vehicle Module
✅ Users Module

These modules further enhance the capabilities of our V4 API, giving you greater flexibility and control over vehicle and user management workflows.

🔍 Highlights:

🚗Vehicle Module

1. Add a new vehicle
2. Retrieve all vehicles
3. Get details of a specific vehicle
4. Update vehicle information
5. Delete a vehicle

👤 Users Module

1. Create a new user
2. Retrieve all users
3. Get a specific user’s details
4. Update full or partial user information
5. Delete a user

🧩 Built on the Robust V4 API Architecture:

1. Streamlined request/response formats
2. Enhanced performance and scalability
3. Serverless-friendly integration approach
4. Comprehensive, developer-first documentation

We’re excited to roll out Phase 2 of our Webhook Documentation, now available on the Azuga Developer Portal!
This update brings expanded details and greater clarity, making it easier than ever to implement and manage webhook events effectively.

📘 What’s Included in This Phase:
Each documented event now includes the following key details:

  🔹 Webhook Categorisation  - Classification of Webhook Events Based on Module Features
  🔹 Event Name
  🔹 Event Description
  🔹 Subscription Package if Required
  🔹 Trigger Condition – When and why the event triggers
  🔹 Payload – Full event payload structure
  🔹 Payload Reference – Field-level descriptions and examples

📡 Published Event Categories (with more to come!):
We’ve started with a solid set of core webhook events:

   ✅  Alert Events
   ✅  Asset Events
   ✅  Device Events
   ✅  Equipment Events
   ✅  Driver Events
   ✅  Role & User Events

This is just the beginning—more events will be added in the future to expand integration capabilities.

1. Explore Equipment API Documentation, now part of the V4 API architecture, delivers
   seamless integration, enhanced performance, and reliability for all users.
2. The enhanced Equipment Tracking API offers improved documentation, including detailed
   descriptions of requests, responses, data types, and example payloads to simplify
   integration. These updates ensure clearer implementation and a smoother experience for
   developers.
3. The Equipment Tracking API documentation includes all modules, such as Equipment, BLE
   Beacons, Pairings, Categories, Locations, and Live Map, ensuring ease of integration with
   comprehensive developer documentation.

Use this API to obtain a new access token. To understand how to refresh your token for continued access, refer to the refreshToken API documentation.

New API: Introduced the viewEvents API to provide enhanced functionality for subscribing to webhook events.

Response and Request Descriptions: Improved the request and response descriptions for all APIs under webhook module

400 Error Responses: Updated the response objects for 400 status codes across all APIs to provide more informative error messages.

API Descriptions: Enhanced the overall verbiage in the API descriptions for better clarity and understanding.