Terminal · AsyncAPI Specification

Terminal Telematics Webhooks

Version

View Spec View on GitHub CompanyTelematicsDataFleet ManagementInsuranceAsyncAPIEvents

AsyncAPI Specification

Raw ↑
generated: '2026-11-15'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.withterminal.com/guides/webhooks.md
sources:
- https://docs.withterminal.com/guides/webhooks.md
- https://docs.withterminal.com/api-reference/webhook-events/overview.md
- https://docs.withterminal.com/api-reference/webhook-events/connection-created.md
- https://docs.withterminal.com/api-reference/webhook-events/connection-disconnected.md
description: Terminal provides webhook callbacks for a variety of resource events. Deliveries are signed (verification via Svix) and retried according
  to Svix's schedule.
events:
- event: connection.created
  description: Emitted when a connection is successfully created with a provider account.
- event: connection.disconnected
  description: Emitted when a connection is disconnected. This typically happens if credentials are deemed invalid and the user must re‑authenticate.
- event: connection.reconnected
  description: Emitted when a previously disconnected connection is re‑established.
- event: connection.completed
  description: Emitted when a connection setup process completes.
- event: connection.updated
  description: Emitted when a connection's details are updated.
- event: connection.pending_deletion
  description: Emitted when a connection is marked for deletion.
- event: connection.deleted
  description: Emitted when a connection has been permanently deleted.
- event: sync.requested
  description: Emitted when a sync operation is requested.
- event: sync.started
  description: Emitted when a sync operation starts.
- event: sync.completed
  description: Emitted when a sync operation completes successfully.
- event: sync.failed
  description: Emitted when a sync operation fails.
- event: connection.first_sync_completed
  description: Emitted when the first sync for a connection completes.
- event: delivery.requested
  description: Emitted when a delivery is requested.
- event: delivery.started
  description: Emitted when a delivery starts.
- event: delivery.failed
  description: Emitted when a delivery fails.
- event: delivery.completed
  description: Emitted when a delivery completes successfully.
- event: issue.reported
  description: Emitted when an issue is reported.
- event: issue.resolved
  description: Emitted when an issue is resolved.
- event: provider.availability_updated
  description: Emitted when a provider's availability status is updated.
- event: unsupported_provider.requested
  description: Emitted when an unsupported provider is requested.
- event: link.analytics_event_emitted
  description: Emitted when a link analytics event occurs.
- event: vehicle.added
  description: Emitted when a vehicle is added.
- event: vehicle.modified
  description: Emitted when a vehicle is modified.
- event: vehicle.removed
  description: Emitted when a vehicle is removed.
- event: driver.added
  description: Emitted when a driver is added.
- event: driver.modified
  description: Emitted when a driver is modified.
- event: driver.removed
  description: Emitted when a driver is removed.
- event: trailer.added
  description: Emitted when a trailer is added.
- event: trailer.modified
  description: Emitted when a trailer is modified.
- event: trailer.removed
  description: Emitted when a trailer is removed.
- event: safety_event.added
  description: Emitted when a safety event is added.
- event: safety_event.modified
  description: Emitted when a safety event is modified.
delivery:
  signature: Verify request authenticity using the signature header provided by Svix (see Svix documentation).
  retries: 'Svix retry schedule: attempt 1 immediately, 2 after 5 s, 3 after 5 min, 4 after 30 min, 5 after 2 h, 6 after 5 h, 7 after 10 h, 8
    after 10 h; stop after a 2xx response or when the `webhook-delivery: abort-message` header is returned.'
docs: https://docs.withterminal.com/guides/webhooks.md

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/terminal-telematics-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.