Reference · built on requestConnectorFleet & telematics

Azuga

Vehicles, drivers, maintenance service entries, alerts, and SafetyCam events from Azuga Fleet through the v4 REST API and webhooks.

Request accessPricing ↗

About

Azuga Fleet pairs plug-in vehicle trackers and SafetyCam dash cams with a web console, and its Fleet v4 API exposes what that console holds: vehicles, drivers, users, assets, equipment, BLE beacons, service entries, alerts, and SafetyCam events. Requests go to https://sls.azuga.com/api/v4 as JSON over HTTPS, and webhooks post GPS, trip, fuel, and driving events to a URL you register.

Through Fibric, an operator reads service history and camera events and proposes a service entry, an alert policy change, or a media request. You approve. The write lands once, with a receipt of what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Azuga and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Vehicles through GET /vehicles with vehicleName, vin, make, model, year, groupName, latitude, longitude, currentSpeed, currentOdometerReading, driverName, and deviceSerialNumber
  • Drivers and users through GET /drivers and GET /users, with offset and limit pagination
  • Service entries through GET /service-entries, filtered by startTime, endTime, entityId, and serviceTypes, with odometer, cost, and service center
  • Alerts and alert policies through GET /alerts and the alert-policies endpoints, including alertTypeName and alertCriteria
  • SafetyCam events through GET /safetycam/events, such as CAM_IMPACT, CAM_DISTRACTED_DRIVING, HARD_BREAKING_MESSAGE, and HARD_ACCELERATION_MESSAGE, with media links
  • Webhook events including GPS Message, Trip Start, Trip End, Over Speeding, Hard Braking, Low Fuel, Fuel Increase, Fuel Decrease, and Seat Belt

Proposed actions

  • Target capability: propose a service entry through the create service entry endpoint, with service type, odometer reading, cost, and service center
  • Target capability: propose an alert or alert policy through the create and update alert endpoints
  • Target capability: propose a SafetyCam media request for a time range, or archive and restore an event
  • Target capability: propose a vehicle or driver record update through the modify endpoints

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Book service on schedule, not on breakdown

    Service entries hold odometer and date per service type. The operator compares them to the current odometer from GET /vehicles and proposes the next entry for a manager to confirm.

    With Service Interval

  • Coach from camera events

    SafetyCam events carry type, speed, driver, and video links. The operator drafts a coaching note for each distracted-driving or hard-braking event and holds it for review.

    With Coaching Notes

  • Spot a fuel drop that is not a fill-up

    Fuel Decrease and Fuel Increase webhook events arrive with vehicle and time. The operator flags decreases with no trip and proposes an inquiry to the driver's manager.

    With Fuel Anomaly

  • Triage an impact

    A CAM_IMPACT or CAM_ACCIDENT_AI event lands with location and media. The operator requests the surrounding footage and proposes a first incident record for a safety lead.

    With Near-Miss Triage

Requirements

  • An Azuga Fleet account with a user whose credentials, client API key, and client secret are issued for integration
  • Token handling for the 180-day access token and the refresh-token endpoint that renews it
  • For webhooks, an HTTPS receiver that accepts JSON POSTs with Basic Auth or key-based auth
  • SafetyCam devices on the account for the safetycam endpoints and health report
Authentication
A Bearer token from GET https://fleet-rest.azuga.com/api/v4/login, which takes Basic username:password plus clientApiKey and clientSecret headers and returns an access token and refresh token.

Limits

  • SafetyCam event queries are limited to a 31-day window between startTime and endTime
  • The health report returns at most 500 items per page, and list endpoints default to 50 with offset paging
  • Some webhook events note a subscription package requirement in their documentation
  • The v4 reference lists no trips or breadcrumb endpoint; trip boundaries arrive as Trip Start and Trip End webhook events

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Azuga ↗

Questions and answers

How do I get an Azuga v4 access token?
Call GET https://fleet-rest.azuga.com/api/v4/login with an Authorization header of Basic and the Base64 of username:password, plus clientApiKey and clientSecret headers. The response holds an access token valid for 180 days, a refresh token, and expiry in seconds. Send Authorization: Bearer <accessToken> afterwards.
Which webhook events can I subscribe to?
One webhook can carry several events. The overview lists GPS Message, Over Speeding, Trip Start, Trip End, Low Fuel, Fuel Increase, Fuel Decrease, Battery Low Alarm, Battery Critical Alarm, Connect, and Disconnect. Later documentation adds Hard Acceleration, Hard Braking, Hardcore Braking, Seat Belt, Oil Life Remaining, and vehicle create, update, and delete events.
Does the health report cover engine faults?
No. GET /health/report describes SafetyCam device health: recording status, calibration state, alarm detail, and recommended steps. It does not report diagnostic trouble codes or battery voltage.
Ask about Azuga

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Azuga through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy