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.