Skip to main content
This guide outlines what to have in place before going to production. Not every section will apply — focus on the areas relevant to your use case. How you integrate the Link component depends on your onboarding flow:
  • Digital onboarding flow: Use the SDK to embed the Link component in your application. Ensure you’re handling the onSuccess callback and exchanging the public token for a connection token.
  • Manual outreach (email, text, etc.): Use the Hosted Page and send the link directly to fleets.
Regardless of approach, ensure you have a way to capture new connections — whether via redirect handling, the connection.created webhook, listing connections from the API, or managing them via the dashboard. You should also have a strategy for mapping connections to entities in your system, either by using externalId or tags, or by storing the Terminal connection ID.

​
Connection Lifecycle

​
Data Access

Depending on whether you’re using the API directly or Data Delivery:

​
If using the API

  • Know which endpoints you’re using and what data you’re ingesting.
  • Handle pagination for list endpoints.
  • Track what data you’ve already synced (e.g., using modifiedAfter checkpoints).

​
If using Data Delivery

  • Confirm where and how data is being delivered.
  • Have a process for ingesting incoming data.

​
For historical data use cases

  • Account for late-arriving data with appropriate lookback windows.
  • Handle updates to previously-synced records.

​
Webhooks (if applicable)

If you’re using webhooks, consider which events are relevant to your use case. Key events include: See the full list of events for more options.

​
Product Integration

  • How does Terminal data fit into your product experience?
  • What does your user see or do when they connect their telematics?
  • What happens in your product when data lands?

​
Validation

Before going to production, verify that:
  • Your consent flow works end-to-end (new connections and re-connections)
  • Data flows into your system after sync completes
  • You have a process for handling disconnected connections
  • Terminal data surfaces correctly in your product