Skip to main content

Events, Profiles & Gateway Routes

Beyond polling and live telemetry, Destiny lets you control which events are monitored per client and where data is routed to external systems.

Event Profiles​

An Event Profile defines the set of events monitored for a client, organised by channel. Use the Event Profiles operations to:

  • Create a profile for a client (Add Event Profile) or clone an existing one (Clone Client Event Profile).
  • List the available channels (Event Profiles Client Channel Listing, Event Profiles Monitored Channel Listing).
  • Add, update or remove individual events on a profile (Add Event Profile Event, Update Event Profile Event, Delete Event Profile Event).

This is how you tune what counts as a reportable/alertable event for a given customer.

Event Pools & history​

Historical event data is queried through the History Query API (event counts over a period, by unit, unit type, model, driver, or total). See the API Reference → History Query API for the event-count operations, and the Event Pools operations in the HTTP API.

Gateway Routes & API Bridges​

To forward data to external systems, Destiny provides:

  • Gateway Routes — configure routing of data out of the platform (Get Gateway Routes Listing, Get A Gateway Route, create/edit forms).
  • API Bridges (Webfleet) — integrate with Webfleet via dedicated bridge endpoints (Create API Bridge, Update, Delete, plus create/edit forms).

These are the integration seams for pushing Destiny data into third-party fleet or telematics systems.

note

Each operation's exact parameters and payloads are documented under Event Profiles, Event Pools, Gateway Routes and API Bridges - Webfleet in the API Reference.