Accounting & payments
QuickBooksAdapter built; OAuth activation required
XeroAdapter built; OAuth activation required
StripeBuilt; account and webhook activation required
ACH / card processingBuilt through Stripe; account activation required
Stripe ConnectBuilt; Connect onboarding required
Telematics & ELD
SamsaraAdapter built; tenant credential acceptance required
GeotabAdapter built; tenant credential acceptance required
Verizon ConnectAdapter built; tenant credential acceptance required
MotiveAdapter built; tenant credential acceptance required
ELD providersImport contract built; provider acceptance required
Maps & routing
Mapping & geocodingAdapter built; provider key required
Live trafficAdapter built; provider plan required
Address validationAdapter built; provider key required
Hardware & scales
Smart-bin ingestBuilt; device and field acceptance required
High-volume IoT ingestionReference-tested above 2M readings/day
GPS and roll-off hardwareExternal hardware activation required
Scale-ticket importBuilt
Certified-scale connectionNamed provider and sandbox still required
Comms & notifications
SMS & emailAdapters built; sender/provider configuration required
Customer notificationsWorkflow built; delivery provider required
WebhooksBuilt with signing, retry, and delivery history
Developer
Customer API v1 (7 operations / 6 paths)Built with scoped keys, rotation, rate limits, audit, and idempotent service-order writes
Internal platform API (150+ endpoints)Used by Haultro workspaces and services; not an open customer API contract
WebhooksBuilt
API keys & scopesBuilt
"Built" means the repository implements the contract and failure handling. It does not mean a customer's third-party account is connected. Provider-backed items stay unavailable until credentials, consent, plan eligibility, and sandbox acceptance are complete.
Get started
Bring your stack with you.
Tell us what you run today and we'll map the integration.