01
Map display
Web, mobile and embedded maps with vector or raster tiles, styles, camera, markers, geometry, events, custom layers and 2D/3D presentation.
Cockpit and companionFleet and owner applicationsDealer and operations portals
AutoBuild your programDeveloper docs · APIs
Location and mobility capabilities your stack can compose.
This public orientation describes what the service families do and how to integrate them responsibly. For exact endpoints, parameters and response schemas, use the linked current Mappls documentation and your program contract.
Functional index
Seventeen families. One governed journey context.
Use only the families enabled for your application, territory and commercial entitlement.
02
Autosuggest and text search
Location-biased suggestions, place, address and POI matching with fuzzy, phrase and category behavior.
Destination entryService discoveryIndia-aware address search
03
Geocoding and reverse geocoding
Resolve text or structured addresses to coordinates, and coordinates to address, place and road context.
Address normalizationIncident intakeAsset and dealer records
04
Mappls PIN and eLoc
Resolve, share and open compact location identities for deep-link and cross-device journeys.
Send-to-carTrip sharingPrecise arrival
05
Nearby and category search
Discover POIs, chargers, parking, fuel, service and amenities near a point or route.
Route stopsCharging discoveryRoadside and service
06
Directions
Passenger, bike, truck, pedestrian and EV routing as entitled, including traffic, alternatives, toll, time and distance context.
Trip planningEmbedded navigationField and mobility execution
07
Route matrix
Many-to-many distance, duration and ETA for assignment, dispatch and optimization decisions.
DispatchNearest-resource selectionFleet planning
08
Route optimization
Sequence stops, orders, tasks and visits under distance, time, capacity and operational constraints.
DeliveryField serviceShared and commercial fleets
09
Predictive and historical ETA
Time-dependent route cost using historical and live traffic where available.
Departure planningCustomer promisesControl-tower exception detection
10
Snap to road and map matching
Associate noisy traces with the road graph and recover matched position, road context and route history.
TelematicsTrip reconstructionToll and route analysis
11
Navigation SDK
Map, location, routing and guidance modules or full UI with voice, reroute, lanes, junctions, safety and hybrid/offline patterns.
OEM cockpitCompanion applicationTwo-wheeler and fleet
12
Tracking and mobility
Publish or ingest position, current state, trails, activities, events, driver behavior and geofences.
Connected vehicleFleet controlDriver, rider and workforce
13
Analytics and GIS
Spatial query, catchment, heat, suitability, geofence, private data, custom layers and dashboard services.
Network planningCharging strategyOEM operations
14
RealView
Geo-referenced imagery retrieval and visual location context in entitled territories.
Map verificationOperations inspectionSite and customer context
15
3D and digital twin
3D buildings, terrain, scenes and live operational overlays for entitled data and deployment scopes.
Premium cockpitOperations twinSimulation and planning
16
Application and deep links
Open or share a place, map, route or navigation context between web, mobile, Mappls and OEM applications.
Send-to-carTrip sharingLast-mile continuity
17
Workforce and workflow
Tasks, visits, teams, proof and location-linked field status where entitled.
Roadside assistanceDealer and charging serviceField operations
Request patterns
Examples that teach the integration boundary.
Placeholders are deliberate. Never expose production credentials. Current documentation and entitlement override illustrative code.
autosuggest.sh
curl --get \
'https://search.mappls.com/search/places/autosuggest/json' \
--data-urlencode 'query=Mappls office' \
--data-urlencode 'location=28.454,77.435' \
--data-urlencode 'region=IND' \
--data-urlencode 'access_token=<ACCESS_TOKEN>'Location bias improves relevance. Regional and premium fields are entitlement-dependent.
route.sh
curl --get \
'https://route.mappls.com/route/direction/route_traffic/driving/<START>;<DESTINATION>' \
--data-urlencode 'steps=true' \
--data-urlencode 'alternatives=2' \
--data-urlencode 'region=ind' \
--data-urlencode 'access_token=<ACCESS_TOKEN>'Coordinates use longitude,latitude; Mappls PIN may be supported as an input.
Authentication note
Mappls documentation contains product and release-specific authentication paths, including an updated mechanism introduced in 2025 and legacy OAuth materials. Follow the branch and method specified for your entitled SDK or API; do not infer one universal flow.
Contract checklist
Everything to settle before production traffic.
Convert this list into the technical schedule for the OEM program.
Authentication
Use the credential and authorization mechanism documented for the entitled product release. Separate apps, environments and roles; rotate without vehicle downtime.
Request design
Set explicit region, profile and options. Apply bounded timeouts, safe retries only where appropriate and idempotency for writes or remote actions.
Response handling
Treat optional fields as optional. Check source, freshness, confidence and entitlement before presenting safety, traffic or charger information.
Rate & concurrency
Plan steady, burst and fleet-wide behavior. Back off on throttling and keep the cockpit useful if cloud capacity is unavailable.
Observability
Propagate correlation IDs across vehicle, OEM cloud and Mappls calls. Retain only privacy-safe support context.
Lifecycle
Pin supported contracts, monitor release notes, rehearse key rotation and migration, and maintain model-year compatibility.
Error and fallback
Design every cloud feature with a cockpit-safe answer.
Status codes and exact bodies differ by service. The OEM experience still needs a consistent policy.
Invalid request
Do not retry. Validate the captured input and surface a corrective action.
Unauthorized / forbidden
Stop repeated calls. Refresh or rotate through the approved credential flow; hide unentitled features.
Rate limited
Honor backoff, shed non-critical work and preserve the embedded baseline.
Unavailable / timeout
Use cached or offline behavior when licensed; state freshness and avoid implying live status.
Partial content
Render the guaranteed minimum. Optional fields must not break navigation or vehicle workflows.
Stale data
Show source and freshness for traffic, charger, hazard and safety-relevant content.
OEM program workshop
Bring us the vehicle. Leave with the program shape.
Choose the surfaces, modules, deployment and lifecycle that fit your next RFQ. We will turn it into a focused discovery brief.