Skip to main content

​
Models you plan to use

All provider data is normalized into Common Models, so your integration works the same regardless of which provider a fleet is on. Review the models and decide which ones you need. Plans include different scopes of models. If you’re not sure which ones yours covers, ask your Terminal contact to confirm before you build against them.

​
Your customers’ providers

  • Look up each provider your customers run in the Provider Explorer to see the models and data it supports.
  • Some providers need a one time setup in your provider configuration before customers can connect them. Each one has its own configuration guide under Connect Your Customers. Start there if a provider isn’t showing up for your customers.
  • To limit which providers your customers see in Link, set an include or exclude list with Provider Access Control.
Decide how customers reach Terminal Link: the SDK embedded in your app, or the Hosted Page you send to fleets directly. Consent Templates let you run different flows for different products or customer segments.
Send us your logo. Link shows your application’s branding to every fleet you onboard, so send your Terminal contact a high resolution logo (.png, .svg, or .jpg).

​
How data reaches your systems

Compare the options in Data Replication: pull from the API, have files delivered to Amazon S3, or stream to Kafka. You can use more than one, for example the API for product features and S3 for analytics. Decide how much history you need on each new connection too. See Backfill Duration.

​
Which events you react to

Webhooks tell you when a connection is created, a sync finishes, or data changes, so you aren’t left polling. Decide which events your systems need.

​
How connections map to your system

Every connection gets a Terminal connection ID. Set an externalId or tags with Custom Identifiers so you can find data using the IDs you already have for that customer.

​
Working towards a Production release

Everything above builds toward the Production Readiness checklist, which covers the consent flow, connection lifecycle, data access, webhooks, and billing. It’s where your development ends, so work through the guides and your own development and QA process first, and treat the checklist as the standard you’re building toward. Once you’re confident you’ve covered all of it, let your Terminal contact know. We’ll go through it with you and help provision your production environment.