Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt

Use this file to discover all available pages before exploring further.

​
v2.5.0 - Fleet Connection Webhook Events
21st January 2026
This minor release introduces new webhook event types for tracking fleet connection lifecycle events, enabling you to monitor when fleet-level connections are established in your integration.
Minor Release: This release adds new webhook event types without breaking existing functionality. All changes are backward-compatible additions.

​
New Webhook Events

Added:
  • fleet_connection.created - Triggered when a new fleet connection is established
  • fleet_connection.* - Wildcard pattern for subscribing to all fleet connection events
Use Cases:
  • Monitor fleet-level data ingestion setup
  • Track when new fleet connections become active
  • Automate workflows based on fleet connection lifecycle
Example Webhook Subscription:
{
  "url": "https://your-app.com/webhooks",
  "events": ["fleet_connection.created"],
  "enabled": true
}
Example Event Payload:
{
  "event": "fleet_connection.created",
  "data": {
    "id": "fc_abc123",
    "fleet_id": "fleet_xyz789",
    "status": "active",
    "created_at": "2026-01-21T10:30:00Z"
  }
}

​
Documentation Improvements

Enhanced the ConnectionCreated event description to clarify that connections represent data ingestion from Telematics Service Providers (TSPs).Updated Description:
“Connection created event. A connection is how we ingest data from a TSP.”
This clarification helps developers better understand the role of connections in the Catena data pipeline.

​
Migration Guide

1

Review Fleet Connection Events

If your integration monitors connection lifecycle events, consider subscribing to the new fleet_connection.* events for fleet-level visibility.
2

Update Webhook Subscriptions (Optional)

Add fleet connection events to your webhook configuration if you need fleet-level connection tracking:
POST /v2/webhooks
{
  "url": "https://your-app.com/webhooks",
  "events": [
    "connection.*",
    "fleet_connection.*"
  ]
}
3

Test Event Handling

Ensure your webhook handler can process the new event types, or safely ignore them if not needed.
No Action Required: Existing integrations continue to work without changes. The new event types are purely additive.

​
Need Help?

API Reference

View complete endpoint documentation with current API structure

Contact Support

Questions about migrating your integration? Our team is here to help