Phone, SMS & business messaging
VoIP/telephony, SMS, business messaging and email providers
Keep the provider you already use where its API supports the calls, messages or events you need TDH3 to handle.
Bring your existing providers
Keep the systems that already work for your business.
TDH3 is designed so customers do not have to replace a telematics, phone, accounting, mapping or signing provider simply to use the platform. We confirm how the provider connects and what its API actually supports before anything is described as live.
A provider is only called Supported after its TDH3 adapter and required capabilities have been built and tested.Three clear statesNo false promises
1
SupportedA TDH3 adapter already exists and has been tested for this provider and capability.
Ready2Compatibility checkThe provider may be connectable, but TDH3 must confirm its API, permissions, data and account requirements first.
Check3Custom / specialistThe provider or workflow needs separately scoped integration work before it can be used live.
ScopeWhat TDH3 can assess
Connect the provider you already use where its interface allows it.
These areas are integration-ready at platform level, but a real provider is not treated as plug-and-play until its adapter is confirmed.
Telematics & GPS
Vehicle tracking, asset location, mileage, engine hours and provider events
TDH3 can consume authorised provider data where the tracking platform exposes suitable APIs, webhooks or structured feeds.
Accounting
Customers, invoices, credits, payments and agreed accounting data
The aim is to keep the customer's existing accounting package and connect only the agreed data flows that the provider supports.
Mapping & routing
Address lookup, geocoding, distance, routing and multi-stop planning
A standard or customer-selected provider can be used where its commercial terms and API capabilities fit the required workflow.
E-signature
Signature requests, status updates and completed document return
Existing signing providers can be assessed where they provide an API or webhook model suitable for the required TDH3 document flow.
Connection methods
What we can readily work with.
The provider must permit the connection and expose the data or actions the customer actually needs.
OAuth
The customer signs in with the provider and grants TDH3 authorised access without sharing a password.
API key or token
Suitable where the provider issues documented server-side credentials for the customer's own account.
REST API
TDH3 can read or send agreed data where the provider exposes a documented API and the customer's plan permits access.
Webhooks
Useful for near-real-time provider events such as messages, status changes or telematics observations.
SFTP or scheduled files
Can suit providers that supply structured files but do not offer a modern API.
CSV / spreadsheet exchange
Useful for controlled import or export when a live integration is not available.
Check the interface
Does the provider offer a documented API, OAuth connection, webhook or structured data feed?
Check the customer’s plan
Does the customer's existing subscription include the required API access?
Confirm the data flow
What exact data can TDH3 read, send or receive and how quickly is it updated?
Confirm costs and limits
Are there provider charges, usage limits, restrictions or third-party approval requirements?
Before go-live
Provider compatibility is confirmed during onboarding.
Tell us the systems you currently use. TDH3 checks the provider, the customer’s account level, the available API or data connection, any third-party charges and the exact read/write scope. If an adapter already exists and is tested, it can be treated as a supported integration. If not, we confirm whether it is a straightforward compatibility job or separately scoped custom work.
API keys, OAuth refresh tokens, passwords and private credentials are never intended to be stored in ordinary customer workspace fields. Live credentials belong in approved server-side integration storage.