canonical: https://jentic.com/apis/telematicssdk.com/quick-start---telematics-sdk # Telematicssdk Quick start - Telematics SDK Introduction We have prepared a set of APIs for quick start to integrate telematics SDK that powers mobile telematics inside 3rd party mobile applications. * [CONTACT US](https://telematicssdk.com) * [SANDBOX](https://userdatahub.com) * [DEV.PORTAL](https://docs.telematicssdk.com) * [DEMO APP](https://raxeltelematics.com/telematics-app) Overview Datamotion provides telematics infrastructure for mo. The API exposes 9 endpoints. ## For AI agents Programmatically trips - trip details, `/v1/scorings/consolidated.` Covers 9 operations. ## Scope Does not handle payments, communications, or developer tools - use for crm only. ## Capabilities - Trips - trip details - `/v1/Scorings/consolidated` - User safe scoring - Accumulated value - v1/Scorings/individual - `/v1/Statistics/consolidated` - Monitor Quick start - Telematics SDK operational status and events ## Use cases ### CRM Operations Use the Quick start - Telematics SDK to perform crm operations programmatically. The API provides 9 endpoints covering core functionality including trips - trip details, `/v1/scorings/consolidated`, `/v1/scorings/consolidated/daily.` Example prompt: Call GET `/mobilesdk/stage/track/get_track/v1` to trips - trip details ### Automated 1. User management (Required) Management Automate 1. user management (required) operations by combining multiple Quick start - Telematics SDK endpoints. Agents can `/v1/scorings/consolidated` and then `/v1/scorings/consolidated/daily` in a single workflow. Example prompt: Call GET `/statistics/v1/Scorings/consolidated` to `/v1/scorings/consolidated`, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Quick start - Telematics SDK endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'trips - trip details', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/mobilesdk/stage/track/get_track/v1` | Trips - trip details | | GET | `/statistics/v1/Scorings/consolidated` | `/v1/Scorings/consolidated` | | GET | `/statistics/v1/Scorings/consolidated/daily` | `/v1/Scorings/consolidated/daily` | | GET | `/statistics/v1/Scorings/individual` | User safe scoring - Accumulated value - v1/Scorings/individual | | GET | `/statistics/v1/Scorings/individual/daily` | User safe scoring - daily value - `/v1/Scorings/individual/daily` | | GET | `/statistics/v1/Statistics/consolidated` | `/v1/Statistics/consolidated` | | GET | `/statistics/v1/Statistics/consolidated/daily` | `/v1/Statistics/consolidated/daily` | | GET | `/statistics/v1/Statistics/individual` | User statistics - Accumulated value - `/v1/Statistics/individual` | ## Key resources - **1. User management (Required)** — # Introduction if you build an integration when all statistics data coming from your own server, onl - **2. For mobile app (Optional)** — # Introduction These API services designed to use it inside a mobile applications to get statistics - **2.1. User statistics (Optional)** — Operations related to 2.1. User statistics (Optional) - **2.2. User trips (Optional)** — Operations related to 2.2. User trips (Optional) - **2.3. User eco scoring (Optional)** — Operations related to 2.3. User eco scoring (Optional) ## Why Jentic - **Setup:** Wiring the Telematics SDK API by hand still means writing the HTTP client, date-range query building, and retry handling for its scoring and statistics endpoints yourself. Through Jentic you install once, import the Telematics SDK API from the API Directory, and your agent calls it. - **Permission scoping:** The Telematics SDK API exposes read endpoints keyed by query parameters rather than resource ids in the path, so limit the agent to the operations it needs, such as reading consolidated scorings or daily statistics. You choose that allowed set, and only the read operations you name are available to the agent. - **Credential handling:** Any Telematics SDK credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get consolidated driving scores' or 'read daily statistics', and Jentic returns the matching Telematics SDK API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hubspot** — Alternative crm API - **Salesforce** — Alternative crm API - **Pipedrive** — Complementary crm API - **Zoho** — Complementary crm API ## FAQ ### What authentication does the Quick start - Telematics SDK use? The Quick start - Telematics SDK uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I trips - trip details with the Quick start - Telematics SDK? Yes. Use the GET `/mobilesdk/stage/track/get_track/v1` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Quick start - Telematics SDK? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I trips - trip details through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'trips - trip details'. Jentic returns the matching Quick start - Telematics SDK operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Quick start - Telematics SDK have? The Quick start - Telematics SDK exposes 9 endpoints covering 1. user management (required), 2. for mobile app (optional), 2.1. user statistics (optional) operations. ### Can I limit what my agent is allowed to do with the Telematics SDK API? Yes. Because you run Jentic One yourself, your own rules decide which Telematics SDK API operations and credentials the agent can use. The API exposes only read endpoints keyed by query parameters, so you can allow just the operations the agent needs, such as reading consolidated scorings or daily statistics, and withhold the rest. Only the read operations you name are available to the agent.