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.