Developer & IT
Technical integrations — SSO, AEMP, API, and BI.
The plumbing layer. Single sign-on with Google and Microsoft for IT-managed user identity. AEMP 2.0 telematics data spec for mixed-fleet data exchange with OEM dashboards. A public REST API with webhook subscriptions for your dev team. Custom reports our team develops using AI to spec for your BI team. One page, all the technical hooks.
Identity
Single sign-on — Google & Microsoft
Google SSO: Google Workspace identity via standard OAuth. Users authenticate against Google and arrive at Teletrack already signed in.
Microsoft SSO: Microsoft 365 / Entra ID via standard OAuth. Same experience for Microsoft-shop customers.
Configured by your IT admin at platform setup. We provide service-provider metadata; your admin provisions Teletrack inside your IdP's app catalogue and assigns users/groups.
Users are still created manually or imported via CSV. Custom IdPs (Okta, custom OIDC, Azure AD direct) are possible via custom development.
Data exchange
AEMP 2.0 — mixed-fleet telematics standard
AEMP 2.0 (ISO 15143-3) is the industry-standard data specification for telematics. It defines a common XML/JSON schema for equipment data — location, engine hours, fuel level, fault codes, idle time — so data from different telematics vendors can be consumed by a single OEM dashboard without vendor-specific code.
Teletrack exposes an AEMP 2.0-compliant feed of equipment data. Used by OEM dashboards (CAT VisionLink, Komatsu Komtrax, Volvo CareTrack, John Deere JDLink) and third-party fleet platforms consolidating data across multiple vendors.
In scope: Equipment-level telematics — position, engine hours, fuel, idle, fault codes, basic utilisation metrics. Teletrack-specific features outside AEMP (PROSTART® records, hire customer portal events) use the public API instead.
Programmatic access
Public REST API + webhooks
Authenticated REST endpoints
Asset records, telemetry, pre-start records, fault events, work orders, customer master, alerts, geofences, scorecards.
Webhook subscriptions
Event-driven push: asset events, pre-start events, fault events, work orders, alerts.
Per-endpoint permissions
API key per integration; scope permissions as needed.
Webhook signing
Payloads signed with shared secret so you can verify the source.
Used by: Engineering teams building data lakes, customers integrating with internal job management/dispatch systems, ERP/EAM integrations beyond standard packaged ones, whitelabel partners building branded customer tools on Teletrack data.
Not published yet: Specific rate limits (in dev docs only), public sandbox environment (provisioned per evaluation today; on roadmap).
Business intelligence
Custom reports built for you using AI — to spec
Custom reports our team develops using AI on request — to your specification by our professional services team. We design the reports against your business questions, build them against Teletrack data, and hand over documentation so your team can maintain and extend them.
Typical builds: Executive utilisation reports, cost-per-engine-hour analysis, hire revenue reports, safety performance reports (pre-start failures, incident frequency, geofence breaches), tender-evidence reports.
Pricing: Professional services engagement, quoted case-by-case based on scope, complexity, number of reports, and data refresh cadence.
Self-serve alternative: Build your own reports and pull Teletrack data via the public API. We don't gatekeep — API access is included in standard subscription.
Who uses these technical integrations
Enterprise IT teams running multi-platform stacks. Customers building internal BI/data warehousing into Snowflake, BigQuery, Databricks. Customers with internal engineering teams wanting direct platform access. Tier 1 operators consolidating multi-OEM equipment data via AEMP 2.0. Whitelabel partners (OEM-branded products run on Teletrack today).
Technical integrations FAQs
Can I use my own SSO provider (Okta, custom OIDC, Azure AD direct)?
Not as standard. Google Workspace and Microsoft 365/Entra are the two standard IdPs today. Others are possible via custom development through AS Digital. Scope and quote case-by-case.
How do I pull Teletrack data into our data lake/warehouse?
Public API (pull): Your warehouse ETL hits our REST endpoints on your cadence.
Webhooks (push): We POST events to your endpoint; your warehouse ingests them.
AEMP 2.0 feed: For equipment data, the standard AEMP schema is often the cleanest path.
Most enterprises use a mix — webhooks for event-driven workflows, periodic API pulls for reconciliation.
Can I build custom reports on standard pricing?
Yes: Pull Teletrack data via the public API and build your own reports on standard subscription pricing — API access is included.
Or we build it: Professional services engagement, quoted separately. Our team develops these custom reports using AI. Many customers start by having us build the first set, then hand them to their BI team for ongoing maintenance.
Are there rate limits on the API?
Yes — but specifics aren't published on the marketing site. They're in the dev docs; your Implementation Consultant confirms the right limits for your use case. If you've got high-throughput integration in mind, tell us during evaluation so we can size correctly.
Does AEMP 2.0 cover everything Teletrack does?
No. AEMP 2.0 is equipment-telematics — position, engine hours, fuel, idle, fault codes, basic utilisation. Teletrack-specific features outside that scope (PROSTART® records, hire customer portal events) don't flow through AEMP. Use the public API for those.
Want a walkthrough tailored to your fleet?