Skip to main content

SmartFleet webhooks

Overview​

SmartFleet delivers alert notifications over the same Webhook registry used by other Verifik products. When a watch rule includes the webhook channel, Verifik sends an HTTP callback with a typed fleet_alert_* event.

Also available: Versión en español.

How the target URL is chosen
  1. If the watch rule has a webhookUrl, Verifik looks up an active client Webhook whose URL matches (or falls back to the first active webhook when resolving delivery).
  2. Otherwise the client's first active Webhook endpoint is used.
  3. If no webhook can be resolved, delivery is recorded as skipped with no_webhook_configured.

Register endpoints under Webhooks in the dashboard, then select the webhook channel on a SmartFleet watch rule.

Event type​

fleet_alert_{alertType}

Examples:

Event typeWhen it fires
fleet_alert_soat_expiringSOAT enters the warning window
fleet_alert_soat_expiredSOAT is past expiry
fleet_alert_rtm_expiringRTM enters the warning window
fleet_alert_rtm_expiredRTM is past expiry
fleet_alert_new_comparendoNew traffic ticket detected
fleet_alert_fine_amount_changedTicket amount changed
fleet_alert_ownership_changedOwnership data changed
fleet_alert_new_claimNew insurance claim detected
fleet_alert_check_failedA scheduled check failed
fleet_alert_customCustom / unclassified alert

Payload shape​

Deliveries use the product webhook envelope. The event body includes:

{
  "type": "fleet_alert_soat_expiring",
  "object": {
    "alertId": "66f0…",
    "type": "soat_expiring",
    "severity": "warning",
    "title": "SOAT expires in 12 days",
    "detectedAt": "2026-08-03T18:00:00.000Z",
    "payload": {},
    "asset": {
      "id": "66f1…",
      "plate": "ABC123",
      "vin": null,
      "nickname": "Truck 1",
      "group": "north",
      "country": "co"
    }
  }
}

Exact top-level wrapping follows the shared Webhook Events delivery format used by other Verifik products (type + entity body). Treat new optional fields as additive.

Channels and delivery status​

Each alert stores per-channel outcomes (email, webhook, inApp) with status pending | sent | failed | skipped. In Smart-Agent you can see these on the fleet Alerts list and on each vehicle detail → Alerts tab.