Skip to main content

Integrations

Integrations holds the organisation's webhooks and its audit log.

Webhooks​

A webhook sends events to your system as they happen: alerts, geofence crossings, dispatch, driving hours, fuel and maintenance events.

  1. New webhook → an HTTPS endpoint, the events → Create. Its signing secret is shown once.
  2. Send test: a test event, with the delivery's status.

Webhooks lists the subscriptions (never their secrets), and the deliveries with their retry log.

  • Every delivery is signed. Your system checks the signature with the secret; the developer site shows how.
  • An endpoint that is down is retried with backoff, and each attempt logged. A delivery can be replayed.
  • An endpoint that answers 410 Gone is disabled, with the reason.
  • A rotated secret signs the next delivery.

Owners and admins create webhooks. A viewer is not offered New webhook.

What is built in​

Included with every organisation, free: the device codecs, ZATCA e-invoicing, toll and fine imports, fuel refuels and drains. The manager app's Integrations lists them, with the adapters installed.

Adapters from the marketplace​

Adapters published by other companies are installed and managed in Adapter Studio; see Marketplace and adapters.

Codec readiness in the Console​

The installed-adapters view in Integrations shows your current organisation's codec installation state alongside Codec preparation. The details include the target version, attempt count, available check times and the last reason, separately from connector health.

  • The current installation and an upgrade target may have different states. A prepared version can remain suspended, or keep running while a replacement is pending. Complete describes the target's preparation; read the current-version receipt message separately.
  • Legacy means the current version has no preparation receipt. Existing bindings are preserved without inventing a successful check; the label does not mean the device failed.
  • Checked records a preparation result, including a failed one. It is not a live device-health timestamp.
  • Preparation not reported means the registry did not supply usable preparation information. An unfamiliar state is unknown; neither means the codec passed or that a device is connected.
  • If the installed list cannot be read, it is unavailable rather than empty. Check again before assuming an adapter was removed.

Use Adapter Studio for confirmed retries, upgrades, settings and installation actions; see Codec preparation for eligibility and confirmation details.

Manager web and phone app​

Manager web and the manager app’s web showcase show the same preparation evidence as the Console, separately from installation state and the current version. The display is read-only; retry and upgrade actions remain in Adapter Studio. See Detailed codec preparation for the fields and how to read them; continue using Adapter Studio for installation actions.

For developers​

API keys, OAuth apps, sandboxes and webhooks in one place: For developers.