What this surface enables
A Mappls rest api for routes navigation, tracking telematics, capture feedback, identity platform across REST.
The source identity names a provider-backed durable operations family whose records or lifecycle survive a single request or screen.
Authority: Source Identity · Evidence: intouchREST
Routes NavigationTracking TelematicsCapture FeedbackIdentity Platform
No fenced language tags in the source README
Oauth2
Prepare the integration
- A trusted backend or API client capable of HTTPS requests
- OAuth client credentials issued for the intended Mappls project
Operate the whole lifecycle
This operational model supplements the repository-level setup instructions. Adapt its resource names and transitions to the owning product contract.
Create the owning project, enable entitlements, restrict credentials, and record the resource owner.
Create the SDK, session, asset, task, workspace, or other durable aggregate exactly once.
Persist provider and application identifiers and transitions; make commands idempotent and observations replayable.
Reconcile restarts, delayed events, expired credentials, partial sync, and version changes against durable evidence.
Revoke access and release runtime resources while preserving required history and audit evidence.
Topics documented by the source
01Prerequisites for Using InTouch APIs
Before consuming the InTouch APIs, ensure the following prerequisites are met:
02Mappls Console Login
Developers must log in to the Mappls Console to manage subscriptions and API access. - If the developer already has a registered email ID, they can directly log in to the Mappls Console. - From the console, developers can click the subscribe to InTouch button from the credentials tab inside the Project.
03Client Credentials (CI & CS)
After subscribing to InTouch, developers get access to the InTouch APIs and can be accessed using: - Client ID (CI) - Client Secret (CS)
These credentials are mandatory for authenticating and accessing the InTouch APIs. They also provide access to the default enabled APIs.
04API Access Mapping
• Each Client ID and Client Secret is mapped to a specific project and can only consume APIs associated with that project. - API requests will be rejected if the requested endpoint is not enabled for the associated CI/CS. - Ensure all required APIs are properly mapped before starting integration.
05API Usage Limits
• Some APIs come with default hit limits, which define how many times an API can be accessed within a given period.
06Credential Issuance & Validation
Asset allocation, limit enhancement, and default access–related concerns are managed by the API team. For requesting, validating, or resolving issues related to CI/CS, please contact. apisupport@mapmyindia.com or apisupport@mappls.com
07Authentication Token Generation
• InTouch APIs use Bearer Token–based authentication. - developers must generate a valid Bearer Token using their Client ID and Client Secret through the authentication endpoint by invoking the Token Generation API. - Tokens are time-bound (24 hours) and must be regenerated upon expiration.
08InTouch Fleet Management APIs
This repository contains documentation for Intouch APIs, designed to streamline and optimize fleet management operations. With a focus on real-time tracking, reporting, and performance optimization, these APIs help businesses simplify logistics operations. They integrate critical data such as trip details, device statuses, alarms, historical events, device drive details, device groups, routes and route assignments, geofences, video telematics, charging events, and push event notifications, enabling seamless communication and better decision-making.
By leveraging Intouch APIs, companies can automate complex workflows, improve operational efficiency, and gain valuable insights for proactive fleet management. Whether it is monitoring charging events, receiving push-based event notifications, or tracking driver behavior, these APIs provide a comprehensive solution for managing and monitoring fleets efficiently.
09Table Of Content
• Intouch Alarms APIs - Intouch Charging Events APIs - Intouch Devices APIs - Intouch Drive APIs - Intouch Entities Group APIs - Intouch Events APIs - Intouch Geofence APIs - Intouch Route APIs - Intouch Trip APIs - Intouch Video Telematics APIs - Push Event API
For any queries and support, please contact:
Email us at apisupport@mappls.com
Support Need support? contact us!
[](https://about.mappls.com/blog/)[](https://github.com/Mappls-api)
[](https://twitter.com/mappls)[](https://www.linkedin.com/company/mappls/)[](https://www.youtube.com/channel/UCAWvWsh-dZLLeUU7J9HiOA)
Service references found
URLs are sanitized during ingestion and may include documentation or legacy hosts. Use them to trace the source, not as a substitute for the current API contract.
https://about.mappls.com/api/https://apis.mappls.com/console).https://apis.mappls.com/console/#/freetrial-signuphttps://github.com/mappls-api/mappls-rest-apis/tree/auth-legacy/mappls-token-generation-api).https://about.mappls.com/contact/https://stackoverflow.com/questions/tagged/mappls-api)[](https://about.mappls.com/blog/)[](https://github.com/Mappls-api)[https://www.npmjs.com/org/mapmyindiahttps://www.facebook.com/Mapplsofficial)[](https://twitter.com/mappls)[](https://www.linkedin.com/company/mappls/)[](https://www.youtube.com/channel/UCAWvWsh-dZLLeUU7_J9HiOAhttps://about.mappls.com/api/terms-&-conditionshttps://about.mappls.com/about/privacy-policyhttps://about.mappls.com/pdf/mapmyIndia-sustainability-policy-healt-labour-rules-supplir-sustainability.pdfhttps://about.mappls.com/pdf/Health-Safety-Management.pdfhttps://about.mappls.com/pdf/Environment-Sustainability-Policy-CSR-Report.pdf