Get Driving Scores in 5 Lines of Code. Integrate driver safety scoring, trip analytics, and crash detection into any app. Free up to 10K API calls/month.
90-day sandbox included. No credit card. No sales call.
Access driving data, scores, trip records, and engagement services through REST APIs. Data is captured by the Telematics SDK, processed on the Damoov platform, and delivered as structured API responses ready for integration into your products.
curl -X GET "https://api.telematicssdk.com/v1/Trips/{tripId}/Scoring" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"{ "Safety": 82, "Acceleration": 90, "Braking": 75, "Cornering": 88, "Speeding": 95 }Damoov exposes driving behavior and trip telemetry through REST — not vehicle command APIs or OEM CAN data. Data originates from the mobile telematics SDK on the driver's phone.
| Domain | Example endpoints | Data returned |
|---|---|---|
| Trips | Trip list, Trip detail | Route summary, duration, distance, waypoints, events |
| Scoring | Scoring APIs, Safety score | Safety, eco, acceleration, braking sub-scores |
| Events | Crash / accident APIs | Timestamp, severity, location, crash buffer metadata |
| Users / SDK | Create SDK user, Device status | DeviceToken, JWT tokens, permission diagnostics |
| Live tracking | WebSocket live tracking | Real-time lat/lng, driver display name |
| Webhooks | Backend notifications | Push on trip received, enrichment finished, crash filtered |
Auth: User registration & API auth. Full reference: API get started.
The telematics API sits downstream of the mobile SDK: the SDK captures trips on the phone; the API lets your backend list trips, pull scores, subscribe to events, and feed analytics pipelines.
curl -X POST "https://user.telematicssdk.com/v1/Registration/create" \
-H "Content-Type: application/json" \
-H "InstanceId: YOUR_INSTANCE_ID" \
-H "InstanceKey: YOUR_INSTANCE_KEY" \
-d '{"FirstName": "Alex", "LastName": "Dev", "Email": "[email protected]"}Reference: Create SDK user.
curl -X GET "https://api.telematicssdk.com/v1/Trips/{tripId}/Scoring" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"{ "Safety": 82, "Acceleration": 90, "Braking": 75, "Cornering": 88, "Speeding": 95 }Poll: Get started with the trips API.
Push: Configure backend notifications at app.damoov.com/callbacks.
{
"Event": "TrackEnrichmentFinished",
"UserId": "e5f2d616-896d-4610-9bef-9ff823af1275",
"Object": { "Type": "RichTrack", "Url": "https://api.telematicssdk.com/..." }
}Choose your path. Each use case has dedicated API endpoints, scoring models, and documentation.
UBI and pay-how-you-drive programs need per-trip risk signals from day one — not after a hardware install window. The telematics API returns safety and eco scores, mileage, harsh-event breakdowns, and crash notifications for each trip the mobile telematics SDK records on the policyholder’s phone.
Typical flow: register the driver → SDK captures trips automatically → your pricing engine calls Trips/{id}/Scoring or consumes TrackEnrichmentFinished webhooks → scores feed policy renewal or mid-term adjustments.
APIs used: Trip list & detail, Safety/Eco scoring, crash webhooks, statistics.
Docs: Safety score · UBI technical guide
Fleet SaaS products aggregate driver behavior across hundreds of vehicles without installing GPS hardware in each cab. The API supplies trip logs, live position, permission diagnostics, and tag-based order grouping.
Typical flow: drivers run your branded app with the SDK → programmatic tracking limits data to on-duty periods → your dashboard polls trip summaries or streams live GPS via WebSocket → trip tags group multi-day deliveries under one order ID.
BI Integrations — export structured telematics data to your analytics platform
APIs used: Trip log, live tracking, trip tags, permissions monitoring, data export.
Docs: Get started — trips API · Live GPS tracking
Ride-hailing, car-sharing, gig, and consumer mobility apps need engagement and safety features built from smartphone telemetry — not factory vehicle APIs. The telematics API delivers crash detection payloads, driver scoring for reputation systems, Drivecoins-style rewards, and real-time event webhooks your app can react to in seconds.
Typical flow: SDK runs during active sessions → crash or harsh events push to your backend → you trigger in-app coaching, support workflows, or token rewards. Optional Bluetooth OBD adds vehicle diagnostics for fleets that want both phone-based behavior and ELM327 data.
APIs used: Crash detection & FNOL, engagement (Drivecoins, leaderboards), real-time webhooks, user management.
Docs: Accident detection · Drivecoins
Start free, scale as you grow. No surprises.
Tell us about your use case and we will recommend the right integration path for you.
By submitting this form, you agree to our Privacy Policy and Terms of Service.
A per-trip driver risk scoring model that segments drivers and ranks them by risk level. The model works from the first recorded trip and supports flexible configuration — different scoring rules can be applied to multiple driver groups within a single application.
An open-source scoring model is also available, giving your team full control to manage, customize, and maintain it independently.
Driving style and vehicle usage patterns directly affect fuel consumption, tire wear, and overall vehicle operating costs. The eco-driving scoring model benchmarks driver efficiency, enabling comparison across drivers and trips.
Two drivers can use the same vehicle, but different driving styles produce different outcomes — including fuel consumption, brake wear, and tire degradation.
The Statistics API delivers structured telematics metrics for operations, product development, and driver engagement — accessible by both internal teams and end users.
Retrieve driver performance metrics, safety scores, eco scores, and trip-level statistics directly via the API.
Access complete trip history with in-depth trip analysis, including driving events and waypoints. Use this data to power end-user trip views, build analytics dashboards, or feed downstream processing pipelines.
Data is available via API or through a data export service.
Monitor granted SDK permissions and receive notifications when a driver changes them — enabling immediate follow-up if permissions are revoked.
If trips are not being recorded, access detailed diagnostics to identify the root cause.
Data is available via API, subscriptions, or a daily report delivered to your S3 bucket.
Apply tags to categorize trips. Segment trip data and retrieve statistics and scores filtered by tag.
Group multiple trips under a single tag to track performance at the order level. For example, a logistics company can tag all trips tied to one delivery (e.g., Sydney → Melbourne) across several days.
The tag is activated when the driver accepts the job and deactivated when the delivery is completed — enabling order-level statistics and scoring.
Pair a smartphone with vehicle diagnostics data via a Bluetooth OBD (ELM327) adapter to capture both driving behavior and vehicle telemetry.
Driver behavior, location, and vehicle data are collected automatically in the background and combined into a unified dataset for analysis and product integration.
Damoov exposes trip, behavior, and scoring data that fleet management apps consume — trip logs, live GPS, driver scores, tags, and export. It is not a full FMS replacement (maintenance scheduling, fuel cards, HR payroll). Think of it as the telematics data layer your fleet SaaS integrates via REST.
No. The telematics API returns data collected by the Damoov SDK from smartphone sensors (and optional Bluetooth OBD if you enable it in your app). It does not provide OEM cloud APIs for remote lock, EV state-of-charge from the vehicle bus, or factory telematics feeds.
Each trip receives safety and eco scores computed from detected events — acceleration, braking, cornering, speeding, phone use, road type, and time of day. Sub-scores roll into an overall safety rating you can query per trip or aggregate over date ranges. See Safety score.
The mobile telematics SDK captures data on the phone. The telematics API is how your backend accesses that data. You need the SDK to generate data; you need the API for dashboards, insurer pricing, or multi-tenant products. Evaluate both on the SDK page.
The API does not generate trips on its own — it processes and delivers data captured by the SDK in your iOS or Android app. In practice, every production telematics API integration pairs with the mobile telematics SDK: SDK for capture, API for export and aggregation.
Explore the full API reference and start building with Damoov’s telematics data services.
