# Fleet API Documentation > Azuga's Fleet API provides you with exclusive developer access to vehicle intelligence data such as location, fuel, geofence, engine trouble codes, etc., ## Guides: Documentation - [Getting Started](https://developer.azuga.com/docs/getting-started.md): This page will help you get started with our API! - [Units and Metrics](https://developer.azuga.com/docs/units-and-metrics.md) - [Status Codes](https://developer.azuga.com/docs/status-codes.md) - [Postman Collection](https://developer.azuga.com/docs/postman-collection.md): Postman is an API platform for building and testing the REST APIs. You can import the Azuga Postman Collection file directly into Postman to get started with the testing. ## Guides: WEBHOOKS - [Webhook Events](https://developer.azuga.com/docs/webhook-events.md): Below is a structured list of webhook events, each with a short description. Click on each event to view the sample payload. ## Guides: WEBHOOKS [BETA] - [Overview](https://developer.azuga.com/docs/webhook-overview.md): A webhook (also called a web callback or HTTP push API) is a real-time data delivery mechanism that allows applications to receive updates automatically. Instead of actively requesting data, webhooks… - [Accident Detection](https://developer.azuga.com/docs/accident-detection.md): The ACCIDENT_DETECTION event is triggered when the system detects a potential or confirmed vehicle collision based on sensor data received from the device. This event provides detailed crash… - Pairing Events - [Driver Pair Message](https://developer.azuga.com/docs/driver-pair-message.md): The PAIR_MESSAGE event is triggered when a driver successfully pairs with a vehicle through a Bluetooth beacon device. Upon successful pairing, the system generates and publishes the event data to… - [Driver Unpair Message](https://developer.azuga.com/docs/driver-unpair-message.md): The UNPAIR_MESSAGE event is triggered when a driver disconnects from a vehicle that was previously paired via a Bluetooth beacon device. This event notifies the system that the driver is no longer… - Alert Events - [Alert Creation](https://developer.azuga.com/docs/alert-create.md): The Alert Create Event is used to notify whenever an alert is Created. This ensures that any changes in alert conditions, thresholds, or notification settings are captured and processed. - [Alert Deletion](https://developer.azuga.com/docs/alert-delete.md): The Alert Delete Event is used to notify when an alert is deleted. This ensures that any changes in alert conditions, thresholds, or notification settings are captured and processed. - [Alert Updation](https://developer.azuga.com/docs/alert-update.md): The Alert Update Event is used to notify whenever an existing alert configuration is modified. This ensures that any changes in alert conditions, thresholds, or notification settings are captured and… - Asset Events - [Asset Creation](https://developer.azuga.com/docs/asset-create.md): The Asset Create Event is used to notify whenever an asset is created. - [Asset Deletion](https://developer.azuga.com/docs/asset-delete.md): The Asset Delete Event is used to notify whenever an asset is deleted. - [Asset Updation](https://developer.azuga.com/docs/asset-update.md): The Asset Update Event is used to notify whenever an asset's details are modified. - Device Events - [Device Creation](https://developer.azuga.com/docs/device-create.md): The DEVICE_CREATION event is used to notify when a new device is added to account. It provides real-time updates on device provisioning and availability. - [Device Deletion](https://developer.azuga.com/docs/device-delete.md): The DEVICE_DELETE event is used to notify when a device is removed from an account. It provides real-time updates on device deactivation and removal. - [Device Updation](https://developer.azuga.com/docs/device-update.md): The DEVICE_UPDATE event is used to notify when a device's details are modified. It provides real-time updates on device changes. - Driver Events - [Driver Creation](https://developer.azuga.com/docs/driver-create.md): The DRIVER_CREATE event is used to notify when a driver is added to a account. It provides real-time updates on driver activation and records management. - [Driver Deletion](https://developer.azuga.com/docs/driver-delete.md): The DRIVER_DELETE event is used to notify when a driver is deleted from an account. It provides real-time updates on driver deactivation and records management. - [Driver Updation](https://developer.azuga.com/docs/driver-update.md): The DRIVER_UPDATE event is used to notify when a driver's details are modified, It provides real-time updates on changes. - [DTC Message](https://developer.azuga.com/docs/dtc-message.md): The DTC_MESSAGE event is used to notify when a Diagnostic Trouble Code (DTC) is detected by the vehicle. This helps identify potential issues with the engine or other vehicle systems in real time. - Equipment Tracking Events - BLE Beacon Events - [BLE Beacon Create](https://developer.azuga.com/docs/ble-beacon-create.md): This event is used to notify whenever a new BLE Beacon is created in the system, allowing users to organize and manage beacons more efficiently. - [BLE Beacon Update](https://developer.azuga.com/docs/ble-beacon-update.md): This event is used to notify whenever a BLE Beacon details is modified in the system, allowing users to organize and manage beacons more efficiently. - [BLE Beacon Delete](https://developer.azuga.com/docs/ble-beacon-delete.md): This event is used to notify whenever a BLE Beacon is deleted in the system, allowing users to organize and manage beacons more efficiently. - [BLE Equipment Pairing](https://developer.azuga.com/docs/ble-equipement-pair.md): This event is used to notify in real-time when an equipment is paired with a BLE device. - [BLE Equipment UnPairing](https://developer.azuga.com/docs/ble-equipment-unpair.md): This event is used to notify in real-time when an equipment is unpaired with a BLE device. - Category Events - [Category Create](https://developer.azuga.com/docs/category-create.md): This event is used to notify whenever a new category is created in the system for equipment, allowing users to organize and manage equipment more efficiently. - [Category Update](https://developer.azuga.com/docs/category-update.md): This event is used to notify whenever an existing category is updated in the system, ensuring that any modifications to category details are captured. - [Category Delete](https://developer.azuga.com/docs/category-delete.md): This event is used to notify whenever a new category is deleted in the system, allowing users to organize and manage equipment more efficiently. - Equipment Events - [Equipment Create](https://developer.azuga.com/docs/equipment-create.md): This event is used to notify whenever a new Equipment is created, allowing users to organize and manage equipment more efficiently. - [Equipment Update](https://developer.azuga.com/docs/equipment-update.md): This event is used to notify whenever a Equipment detail is updated, allowing users to organize and manage equipment more efficiently. - [Equipment Delete](https://developer.azuga.com/docs/equipment-delete.md): This event is used to notify whenever an Equipment is deleted, allowing users to organize and manage equipment more efficiently. - Extension Events - [Extension 1 End](https://developer.azuga.com/docs/extension-1-end.md): This event is triggered when power through Extension Wire 1 is turned off or disconnected. It marks the end of an auxiliary power input session being monitored and is specific to Asset Trackers. - [Extension 1 Start](https://developer.azuga.com/docs/extension-1-end-copy.md): This event indicates that the device has started receiving power through Extension Wire 1. It is commonly used in asset trackers to monitor the status of auxiliary power inputs, such as ignition or… - [Extension 2 End](https://developer.azuga.com/docs/extension-1-start-copy.md): This event is triggered when power through Extension Wire 2 is turned off or disconnected. It marks the end of an auxiliary power input session being monitored and is specific to Asset Trackers. - [Extension 2 Start](https://developer.azuga.com/docs/extension-2-end-copy-1.md): This event indicates that the device has started receiving power through Extension Wire 2. It is commonly used in asset trackers to monitor the status of auxiliary power inputs, such as ignition or… - Fuel Events - [Fuel Decrease Event](https://developer.azuga.com/docs/fuel-decrease-event.md): Notifies when a fuel drop is detected - [Fuel Increase Event](https://developer.azuga.com/docs/fuel-increase-event.md): To ensure you are promptly informed about refueling, this could be useful for various reasons, such as detecting refueling events or identifying potential anomalies. - [Fuel Level Remaining (%)](https://developer.azuga.com/docs/fuel-level-remaining.md): This webhook provides real-time updates on the current fuel level of a vehicle. It enables to optimize fuel management and avoid running out of fuel unexpectedly. - [Low Fuel](https://developer.azuga.com/docs/low-fuel.md): To stay informed about critical fuel levels and helping users take timely action during a trip. - Geofence Events - [Geofence](https://developer.azuga.com/docs/geofence.md): The GEOFENCE event is used to notify when a vehicle enters or exits a predefined geofence region. It helps monitor vehicle movement in and out of designated areas. - [ENTERED_GEOFENCE](https://developer.azuga.com/docs/entered-geofence.md): The ENTERED_GEOFENCE event is used to notify when a vehicle enters a predefined geofence region, allowing users to track vehicle entry into specific areas. - [EXIT_GEOFENCE](https://developer.azuga.com/docs/exit-geofence.md): The EXIT_GEOFENCE event is used to notify when a vehicle exits a predefined geofence region, helping users monitor vehicle movements outside designated areas. - [Geofence Timer In](https://developer.azuga.com/docs/geofence-timer-notin.md): The GEOFENCE_TIMER_NOTIN event is used to notify when a vehicle remains outside a predefined geofence region longer than the configured duration, helping users track extended absences from designated… - [Geofence Timer Out](https://developer.azuga.com/docs/geofence-timer-notout.md): The GEOFENCE_TIMER_NOTOUT event is used to notify when a vehicle remains inside a predefined geofence region longer than the configured duration, enabling monitoring of extended stays within… - [GPS Message](https://developer.azuga.com/docs/gps-message.md): Sends GPS location or live updates based on the configured tracking interval. - [Hard Acceleration](https://developer.azuga.com/docs/hard-acceleration.md): The HARD_ACCELERATION_MESSAGE event is used to notify when a vehicle experiences a sudden and rapid increase in speed, indicating hard acceleration. This event helps in identifying unsafe driving… - [Hard Break](https://developer.azuga.com/docs/hard-braking.md): The HARD_BREAKING_MESSAGE event is used to notify when a vehicle experiences a sudden and significant reduction in speed, indicating hard braking. This event helps monitor aggressive or unsafe… - [Hard Core Braking](https://developer.azuga.com/docs/hard-core-breaking.md): The HARD_CORE_BRAKING_MESSAGE event is used to notify when a vehicle exhibits excessive hard braking behavior during a trip. - Over Speeding Events - [Over Speeding](https://developer.azuga.com/docs/over-speeding.md): The Over Speeding event is triggered when the vehicle exceeds the configured speed threshold (default 65 kilometers per hour). If the speed threshold is adjusted, the event condition will… - [Over Speeding Ended](https://developer.azuga.com/docs/overspeeding-ended.md): The Over Speeding Ended event is used to notify when the vehicle's speed drops below the configured over speeding threshold. - [Oil Life Remaining (%)](https://developer.azuga.com/docs/oil-life-remaining.md): The Oil Life Remaining event captures the remaining oil life percentage at the end of each trip, helping fleet managers monitor plan servicing effectively. - Posted Events - [Posted Over speeding Event](https://developer.azuga.com/docs/posted-overspeeding-event.md): The POSTED_OVERSPEEDING_EVENT is triggered when a vehicle exceeds the posted speed limit, generating an overspeeding event based on the device’s real-time data. - [Posted Speed Alert](https://developer.azuga.com/docs/posted-speed-alert.md): This POSTED_SPEED_ALERT webhook event is triggered when a vehicle exceeds the posted speed limit as defined by the alert configuration. - [Posted Speed Limit](https://developer.azuga.com/docs/posted-speed-limit.md): The POSTED_SPEED_LIMIT event is triggered when a vehicle exceeds a manually configured speed limit for a specified minimum duration. This speed limit is not derived from the map's posted limit but… - Requested Media Events - [Requested Media Available](https://developer.azuga.com/docs/requested-media-available.md): The REQUESTED_MEDIA_AVAILABLE webhook notifies subscribers when all requested video media from a supported camera has been successfully retrieved from the SD card and is now available in the Azuga… - [Requested Media Failed](https://developer.azuga.com/docs/requested-media-failed.md): The REQUESTED_MEDIA_FAILED event notifies subscribers that a requested video clip could not be fetched from the camera’s SD card or could not be processed successfully. - [Requested Media Partially Available](https://developer.azuga.com/docs/requested-media-partially-available.md): The REQUESTED_MEDIA_PARTIALLY_AVAILABLE event notifies subscribers that the system was able to access some, but not all, of the requested video duration. - [Requested Media Pending](https://developer.azuga.com/docs/requested-media-pending.md): The REQUESTED_MEDIA_PENDING event notifies subscribers that the requested video cannot be retrieved immediately because the camera is offline. Once the camera reconnects, Azuga will attempt to… - [Requested Media Submitted](https://developer.azuga.com/docs/requested-media-submitted.md): The REQUESTED_MEDIA_SUBMITTED event is triggered when a user submits a request to retrieve a video clip from a camera. This event confirms that the system has received the request successfully and… - [Requested Media Unavailable](https://developer.azuga.com/docs/requested-media-unavailable.md): The REQUESTED_MEDIA_UNAVAILABLE event is triggered when a user submits a video request for a camera, but the requested footage does not exist on the camera’s SD card. This means the system attempted… - Role Events - [Role Creation](https://developer.azuga.com/docs/role-create.md): The ROLE_CREATE event is used to notify when a new role is created in the system. Once the role is created at the customer level, the event data is published to the subscribed webhook. - [Role Deletion](https://developer.azuga.com/docs/role-delete.md): The ROLE_DELETE event is used to notify when a role is deleted in the system. Once the role deletion occurs, the event data will be published to the subscribed webhook. - [Role Updation](https://developer.azuga.com/docs/role-update.md): The ROLE_UPDATE event is used to notify when a role is updated in the system. Once the role is updated, the event data will be published to the subscribed webhook. - [Seat Belt](https://developer.azuga.com/docs/seat-belt.md): The SEAT_BELT event is used to monitor seat belt usage during a trip. It helps fleet managers track driver safety behavior by providing the percentage of time the seat belt was worn while the vehicle… - Temperature Events - [Temperature 1](https://developer.azuga.com/docs/temperature-1.md): The TEMPERATURE_1 event is used to report data from the first temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 2](https://developer.azuga.com/docs/temperature-1-copy.md): The TEMPERATURE_2 event is used to report data from the second temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 3](https://developer.azuga.com/docs/temperature-2-copy-5.md): The TEMPERATURE_3 event is used to report data from the third temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 4](https://developer.azuga.com/docs/temperature-2-copy.md): The TEMPERATURE_4 event is used to report data from the fourth temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 5](https://developer.azuga.com/docs/temperature-2-copy-1.md): The TEMPERATURE_5 event is used to report data from the fifth temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 6](https://developer.azuga.com/docs/temperature-2-copy-2.md): The TEMPERATURE_6 event is used to report data from the sixth temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 7](https://developer.azuga.com/docs/temperature-2-copy-3.md): The TEMPERATURE_7 event is used to report data from the seventh temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - [Temperature 8](https://developer.azuga.com/docs/temperature-2-copy-4.md): The TEMPERATURE_8 event is used to report data from the eighth temperature sensor connected to the asset tracker device. It helps monitor environmental or operational conditions based on external… - Trip Events - [Trip Start](https://developer.azuga.com/docs/trip-start-message.md): The TRIP_START_MESSAGE event is used to notify when a vehicle's trip begins. It marks the point when the ignition is turned on. - [Trip End](https://developer.azuga.com/docs/trip-end-message.md): The TRIP_END_MESSAGE event is used to notify when a vehicle's trip ends. It marks the point when the ignition is turned off. - [TPMS Resolved Event](https://developer.azuga.com/docs/tpms-resolved-event.md): The TPMS_RESOLVED_EVENT is triggered when a previously reported tire pressure issue (Low or High) returns to normal levels. Once the system confirms the resolution, it periodically (every minute)… - User Events - [User Creation](https://developer.azuga.com/docs/user-create.md): The User Creation Event is used to notify when a new user is added in the system. - [User Deletion](https://developer.azuga.com/docs/user-delete.md): The User Creation Event is used to notify when a user is deleted in the system. - [User Updation](https://developer.azuga.com/docs/user-update.md): The User Update Event is used to notify whenever an existing user’s details are modified in the system. - Vehicle Events - [Vehicle Pairing](https://developer.azuga.com/docs/vehicle-pairing.md): The VEHICLE_PAIRING event is triggered when a Bluetooth beacon is detected within the vehicle’s proximity, indicating a successful pairing between the beacon and the vehicle. This event also handles… - [Vehicle Creation](https://developer.azuga.com/docs/vehicle-creation.md): The Vehicle Creation event is used to notify whenever a vehicle is created. - [Vehicle Updation](https://developer.azuga.com/docs/vehicle-updation.md): The Vehicle Updation event is used to notify whenever a vehicle is edited or updated. - [Vehicle Deletion](https://developer.azuga.com/docs/vehicle-deletion.md): The Vehicle Deletion event is used to notify whenever a vehicle is deleted. - [Vehicle Backup Event](https://developer.azuga.com/docs/vehicle-backup-event.md): The VEHICLE_BACKUP_EVENT is used to notify when a vehicle has been in reverse (backup) mode during a trip. This event is notified at the end of the trip after the system analyzes the driving data. - [Vehicle Mil Info](https://developer.azuga.com/docs/vehicle-functional-signal-event-copy.md): The VEHICLE_MIL_INFO event is used to report the status of the Malfunction Indicator Light (MIL) at the beginning of a trip. It helps indicate whether the vehicle's engine has detected any issues… - [Vehicle Not Tracking](https://developer.azuga.com/docs/vehicle-not-tracking.md): The VEHICLE_NOT_TRACKING event is used to notify when a vehicle stops transmitting valid location or tracking data. This helps identify vehicles that are temporarily disconnected or experiencing… - [VIN Change](https://developer.azuga.com/docs/vin-change.md): The VIN_CHANGE_EVENT is used to notify when there is a change in the Vehicle Identification Number (VIN) - Tire Pressure Events - [High Tire Pressure](https://developer.azuga.com/docs/high-tire-pressure.md): The HIGH_TIRE_PRESSURE event is generated when a vehicle’s tire pressure rises above the predefined threshold. Once the Tire Pressure Monitoring System (TPMS) detects this condition, the event is… - [Low Tire Pressure](https://developer.azuga.com/docs/low-tire-pressure.md): The LOW_TIRE_PRESSURE event is generated when the Tire Pressure Monitoring System (TPMS) detects that a tire’s pressure has fallen below the predefined threshold set for the vehicle. Once the… - [Pending DTC Info](https://developer.azuga.com/docs/pending-dtc-info.md): The PENDING_DTC_INFO event is generated when the OBD-II system detects pending Diagnostic Trouble Codes (DTCs) in a vehicle. Pending DTCs are early indicators of potential issues that have been… ## API Reference: Authentication - [Authentication Workflow](https://developer.azuga.com/reference/authentication-workflow.md) - [Refresh Token API](https://developer.azuga.com/reference/refresh-token-api.md): Utilise this API to obtain a new access token using the refresh token provided in the Authentication API. Refresh tokens expire after one use. ## API Reference: REPORTS - [Score report](https://developer.azuga.com/reference/scores-report.md): This API allows the user to generate a detailed report of Driver Scores. Each request provides you with an average score for the date you have requested for a driver. - [Alerts report](https://developer.azuga.com/reference/alerts-report.md): This API allows the user to generate a detailed report on all alert types. - [Trips report](https://developer.azuga.com/reference/trips-report.md): This API allows the user to generate a detailed report on the trips taken by your fleet within the time period that is requested for. - [Breadcrumb Report](https://developer.azuga.com/reference/breadcrumbs-report.md): This API allows the user to view the breadcrumb report. - [Diagnostics Report](https://developer.azuga.com/reference/diagnostics-report.md): This API allows the user to view the Diagnostics Report of a vehicle. - [Geofence Report](https://developer.azuga.com/reference/v3-geofence-report.md): This API allows the user to view the Geofence Report of a vehicle. ## API Reference: Assets - [View All Assets](https://developer.azuga.com/reference/view-all-assets.md): This API allows you to view multiple assets and all their associated information in your account which helps you track and manage the asset. - [Create an Asset](https://developer.azuga.com/reference/create-an-asset.md): This API allows you to create an asset and add all its associated information in your account. - [Update an Asset](https://developer.azuga.com/reference/update-an-asset-1.md): This API allows you to update an asset and add all its associated information. You are allowed to update only the assets you have access to. ## API Reference: VEHICLE - [View All Vehicles](https://developer.azuga.com/reference/view-all-vehicles-1.md): This API allows you to view multiple vehicles and all its information to your account which helps you track and manage the vehicle. - [Update a Vehicle](https://developer.azuga.com/reference/update-trackee-add.md): This API allows you to update any number of parameters of the associated trackee (vehicle). - [Latest Location of Vehicles](https://developer.azuga.com/reference/latest-location.md): This API allows you to get the latest location of all vehicles in your account. You are allowed to fetch the details of vehicles you have access to. Pass an empty body parameter if you are looking… ## API Reference: USERS - [View All Users](https://developer.azuga.com/reference/view-users.md): Use this API to view the account information of users. Users are people in your organization that use Azuga for tracking vehicles and reporting on performance and productivity. Driver accounts are… ## API Reference: Drivers - [View All Drivers](https://developer.azuga.com/reference/view-all-drivers.md): Use this API to view the account information of drivers. Driver accounts are also considered as user accounts with limited access to the application. - [Update Driver Details](https://developer.azuga.com/reference/update-driver-details.md): This API allows you to update one or all parameters of a specific driver. ## API Reference: Devices - [View All Devices](https://developer.azuga.com/reference/view-all-devices-1.md): This API provides you with information about all the devices present in your account. You are allowed to view only the devices you have access to. ## API Reference: GROUPS - [View All Groups](https://developer.azuga.com/reference/view-all-groups.md): This API provides you with information about all groups present in your account. ## API Reference: trackme - [Create TrackMe Link](https://developer.azuga.com/reference/create-trackme-link.md): The TrackMe feature allows customers to track a vehicle or driver until they reach the destination address specified while creating the link. This link remains valid for a specified period,… - [Check TrackMe Link Status](https://developer.azuga.com/reference/trackme-check-status.md): This API helps you to check the status of a TrackMe link. You need to pass Azuga customerID & unique identifier(token) of the TrackMe link as a path parameters. - [Get All TrackMe Links](https://developer.azuga.com/reference/get-trackme-links.md): This API helps you to get the details of all the active TrackMe links configured in your account. - [TrackMe - Keep Alive](https://developer.azuga.com/reference/trackme-keep-alive.md): This API enables you to extend the time to live (TTL) from the remaining duration. The duration extension is possible only for active links. Make sure that you are extending the time before the link… - [TrackMe - Delete Link](https://developer.azuga.com/reference/trackme-delete.md): This API enables you to delete an active TrackeMe link. Please note that this is an irreversible action. ## API Reference: GEOFENCE - [Create a Geofence](https://developer.azuga.com/reference/create-a-geofence.md): Use this API to create a geofence. Geofence is a virtual boundary around a geographical area. A geofence can have radius configured up to 10 Miles. Azuga will notify you when your vehicle enters or… - [View All Geofences](https://developer.azuga.com/reference/view-geofences.md): This API provides you with information about all active geofences present in your account. - [Update a Geofence](https://developer.azuga.com/reference/update-a-geofence.md): The update geofence API allows you to edit the details of an existing geofence. Only one geofence can be updated by a single API call. You are allowed to update geofences for those you have access to… ## API Reference: SAFETYCAM - [Live Streaming - Overview](https://developer.azuga.com/reference/live-streaming-overview.md): This page provides an overview of live streaming - how to use, integrate and implement. - [Live Streaming](https://developer.azuga.com/reference/live-streaming.md): This API helps you to request for live streaming from the camera. This feature is available only for Azuga AI cameras with vendorId=15. - [Camera Wakeup](https://developer.azuga.com/reference/camera-wake-up.md): This API helps you turn on the AI camera if the camera is on sleep mode. This endpoint is used when we request live streaming for Azuga AI camera but the camera is on sleep mode. - [View All SafetyCams](https://developer.azuga.com/reference/view-all-safetycams.md): This API provides you with information about all the Dashcams present in your account. You are allowed to view only the Dashcams you have access to. - [Event Videos](https://developer.azuga.com/reference/eventvideos.md): This API allows you to view the details of the event videos generated for your account between a specified timeframe. You are allowed to filter the result by adding vehicleId or userId(driverId) &… - [Create a Request Video](https://developer.azuga.com/reference/requested-videos.md): This API allows you to create a new Request video. You are allowed to provide only a unique name for the field - requestedVideoName. Recommended to use a alpha-numerics for a unique name. You are not… ## API Reference: Alerts - [Delete an Alert](https://developer.azuga.com/reference/delete-alert.md): This API allows you to delete an alert. You are allowed to delete alerts for those you have access to. Only one alert can be deleted per API call and this is an irreversible action. You need to pass… - [Bulk Delete Alerts](https://developer.azuga.com/reference/bulk-delete-alerts.md): This API allows you to delete multiple alerts from your account. You are allowed to delete only alerts you have access to. All alerts including the default alerts can also be deleted by passing… ## API Reference: WEBHOOKS - [Webhook Overview](https://developer.azuga.com/reference/overview.md) - [Create a Webhook](https://developer.azuga.com/reference/create.md): This API can be utilized to Create a webhook and subscribe to specific events. Upon configuration, Azuga will transmit real-time JSON data to the designated endpoint whenever the subscribed events… - [View all Webhooks](https://developer.azuga.com/reference/view-2.md): This API gives you the details of all the webhooks configured in your account. Details of multiple webhooks can be obtained through this API. This API also returns the unique IDs corresponding to… - [View a Webhook](https://developer.azuga.com/reference/view-webhooks-by-id.md): Use this API to get details of a particular webhook. You need to pass the ID (token) of the webhook, while calling this API. Note: To get the ID of a webhook, you must call the View API. For more… - [View Events](https://developer.azuga.com/reference/events-types.md): This API gives you the list of all the events that are supported by our application and that can be used to trigger a webhook. Some of the events that are recorded by the application are - Speeding,… - [Edit a Webhook](https://developer.azuga.com/reference/edit-1.md): Use this API to edit an existing webhook. You need to pass the ID (token) of the webhook in the API call. Only one webhook can be modified per API call. Note: To obtain the ID of the webhook, you… - [Delete a Webhook](https://developer.azuga.com/reference/delete-1.md): This API allows you to delete a webhook, by passing the ID (token) of the webhook in the API call. Only one webhook can be deleted per API call. Also, you can only delete the webhooks for which you… ## API Reference: Configurations - [View all Configs](https://developer.azuga.com/reference/read-configs.md): This API allows the user to view all the device configurations configured in your account ## Changelog - [Maintenance APIs Enhancement](https://developer.azuga.com/changelog/maintenance-apis-enhancement.md) - [Developer Portal Enhancements](https://developer.azuga.com/changelog/api-authentication-upgrade-to-oauth-20.md) - [V4 Alerts API](https://developer.azuga.com/changelog/v4-alerts-api.md) - [Added search fields in V4 Maintenance Module APIs](https://developer.azuga.com/changelog/added-search-fields-in-v4-maintenance-module-apis.md) - [Webhook Documentation - New Events Added](https://developer.azuga.com/changelog/webhook-documentation-new-events-added.md) - [Authentication on v4](https://developer.azuga.com/changelog/authentication-on-v4.md) - [Webhook Documentation Updated with New Events](https://developer.azuga.com/changelog/webhook-documentation-updated-with-new-events.md) - [New Webhook Events Added to Webhook Documentation](https://developer.azuga.com/changelog/new-webhook-events-added-to-phase-2-documentation.md) - [V4 Base Url Changes](https://developer.azuga.com/changelog/v4-base-url-changes.md) - [V4 SafetyCam Health Report APIs](https://developer.azuga.com/changelog/v4-safetycam-health-report-apis.md)