Mappls Auto developer hub

A clear path from first prototype to production vehicle.

Use this hub to understand capability families, integration patterns and the contract decisions that matter in an automotive lifecycle. Endpoint and SDK release details remain governed by the official Mappls developer portal and your entitlement.

Compose, configure or take the complete experience.

Mappls Auto supports different ownership models without treating them as disconnected products.

01

Developer control plane

Create a synthetic OEM project, inspect effective rights, issue one-time sandbox identity and evaluate production evidence.

Explore path →
02

API composition

Call search, route, tracking, analytics and workflow services from OEM cloud or applications.

Explore path →
03

Cross-product interfaces

Trace all 33 products through 20 vehicle, cockpit, cloud, app, content and operations contracts.

Explore path →
04

OEM program readiness

Freeze eight coverage dimensions, seven lifecycle exits, nine verification domains, eight standards families and seven operational domains.

Explore path →
05

Cloud assurance

Review all eleven SaaS products, twenty-two contracts, degraded states, operations and production-release boundaries.

Explore path →
06

SDK integration

Build web, mobile, companion and cockpit experiences from Mappls map and navigation components.

Explore path →
07

Application assurance

Review APP-01 through APP-09 across Android, AAOS, iOS, TypeScript and responsive web, including offline and release boundaries.

Explore path →
08

Turnkey application

Configure a complete Mappls-powered navigation, connected, fleet or mobility experience.

Explore path →
09

Data & embedded

Integrate device-resident map content, navigation runtime, vehicle signals, eHorizon or edge devices.

Explore path →
010

Firmware integration

Inspect all seven edge runtimes, their authority, resource bounds, degradation and cross-runtime release gate.

Explore path →
011

Hardware assurance

Review all six reference designs, software attachment, manufacturing evidence and EVT-to-SOP gates.

Explore path →
012

Portfolio assurance

Trace all 33 products through twelve cross-program evidence and acceptance gates.

Explore path →
013

eHorizon validation

Exercise bounded probable paths, attribute validity, degradation, replay and a non-control safety boundary.

Explore path →
014

Geo operations

Validate precise intake, resource eligibility, provider-source state, closure evidence and reproducible network analytics.

Explore path →

Search. Route. Track. Optimize.

Mappls publicly documents REST services and SDKs across core location functions. Authentication, region, response fields, premium parameters, quotas and version policy depend on the product and agreement.

  • Use separate non-production and production credentials.
  • Keep server credentials out of applications and repositories.
  • Declare territory, fallback and missing-field behavior.
  • Capture request IDs and privacy-safe traces for support.
Explore API families →
search-and-route.sh
# Illustrative: follow your entitled auth method
curl --get \
  'https://search.mappls.com/search/places/autosuggest/json' \
  --data-urlencode 'query=charging station' \
  --data-urlencode 'location=28.454,77.435' \
  --data-urlencode 'access_token=<ACCESS_TOKEN>'

# Use a Mappls PIN or longitude,latitude in route inputs
# Select traffic, vehicle profile and alternatives by contract.

Never paste a production credential into client code or support tickets.

Developer building blocks across NCASE.

The full API page expands scope, common automotive uses and links into the official documentation.

Technical orientation for every product and system.

Each blueprint maps the product to contract families, adjacent interfaces, canonical context, delivery stages and release evidence—without inventing universal endpoints or availability.

01 · SaaS & cloud

Connected Vehicle Cloud

One governed digital twin for every entitled vehicle journey.

Open blueprint →
02 · SaaS & cloud

InTouch & Fleet Control Tower

Turn live vehicle state into an exception-led operating picture.

Open blueprint →
03 · SaaS & cloud

RouteNet Optimization

Plan fewer kilometres—and keep the plan useful when reality changes.

Open blueprint →
04 · SaaS & cloud

Map & Content Cloud

Treat automotive map content as a governed product lifecycle—not a file transfer.

Open blueprint →
05 · SaaS & cloud

Charging Intelligence Operations

Connect EV journey quality with charging-network decisions and field action.

Open blueprint →
06 · SaaS & cloud

Geoanalytics & Command Center

Put assets, incidents, work and location intelligence on one operational map.

Open blueprint →
07 · SaaS & cloud

EV Journey & Charging Cloud

Turn vehicle truth and road context into an energy plan the driver can understand.

Open blueprint →
08 · SaaS & cloud

eHorizon & HD Map Cloud

Deliver versioned road-ahead context with an explicit operational design boundary.

Open blueprint →
09 · SaaS & cloud

Mobility Orchestration Platform

Keep rider promise, driver execution and fleet decision on one trip identity.

Open blueprint →
10 · SaaS & cloud

AI Cockpit Orchestration Cloud

Put deterministic automotive policy between every model and every tool.

Open blueprint →
11 · SaaS & cloud

Automotive Developer & Entitlement Cloud

Make every integration environment, entitlement and release explainable.

Open blueprint →
12 · Native application

Embedded Navigation

A resilient OEM cockpit built around one route truth.

Open blueprint →
13 · Native application

OEM Owner Companion

Make the OEM app useful before, during and after every drive.

Open blueprint →
14 · Native application

EV Cockpit & Companion

Make range explainable, routes energy-aware and charging actionable.

Open blueprint →
15 · Native application

Driver & Field Execution

Join assignment, navigation, task state and support into one trustworthy mobile execution loop.

Open blueprint →
16 · Native application

Fleet & Operations Portal

An operator workspace designed around action, not map clutter.

Open blueprint →
17 · Native application

Dealer, Service & Roadside

Bring precise location and live execution into high-stress ownership moments.

Open blueprint →
18 · Native application

AI Cockpit Assistant

A voice-and-touch assistant whose state never depends on model wording.

Open blueprint →
19 · Native application

Rider & Passenger App

Make the mobility promise clear from pickup search to completed trip.

Open blueprint →
20 · Native application

Automotive Developer Console

Put entitlement, trace and release evidence beside the code that needs it.

Open blueprint →
21 · Embedded software

Location Runtime

A confidence-aware vehicle position that survives difficult roads and signals.

Open blueprint →
22 · Embedded software

Navigation Runtime

The route and guidance engine behind every entitled cockpit surface.

Open blueprint →
23 · Embedded software

Vehicle Signal Abstraction

Make vehicle state usable without coupling every product to every ECU contract.

Open blueprint →
24 · Embedded software

Connectivity & Telemetry Agent

Preserve the right events through the wrong network conditions.

Open blueprint →
25 · Embedded software

Content & Map Update Manager

Activate the right content on the right vehicle—and always know how to recover.

Open blueprint →
26 · Embedded software

Device Lifecycle & OTA Agent

One secure lifecycle from factory identity to end-of-life.

Open blueprint →
27 · Embedded software

eHorizon & ADAS Map Runtime

Deliver qualified road-ahead profiles with freshness, confidence and safe degradation.

Open blueprint →
28 · Hardware system

Line-fit TCU

Automotive-grade identity, positioning and connectivity for the connected vehicle.

Open blueprint →
29 · Hardware system

AIS-140 / Fleet Tracker

A field-resilient operational location device with a governed cloud lifecycle.

Open blueprint →
30 · Hardware system

Dashcam & Video Telematics

Join road or cabin video to the vehicle event that explains why it matters.

Open blueprint →
31 · Hardware system

In-dash Navitainment & IVI

An integrated cockpit system designed around boot, navigation, vehicle and lifecycle reality.

Open blueprint →
32 · Hardware system

Two-wheeler Cluster & HUD

Glanceable rider guidance that respects sunlight, gloves, vibration and attention.

Open blueprint →
33 · Hardware system

Rider Accessory

A connected navigation-adjacent product with an explicit safety and battery boundary.

Open blueprint →

Automotive success lives beyond the happy-path call.

A production integration specifies technical behavior, data rights, quality and operations—not only method names.

Versioning

Contract and schema compatibility, release notes, deprecation and model-year support.

Performance

Availability, latency, rate, burst, timeout, retry, idempotency and failover.

Content

Territory, version, update, freshness, attribution, caching and offline rights.

Errors

Taxonomy, deterministic fallback, confidence and provenance where applicable.

Operations

Request IDs, dashboards, logs, incident communication, test data and replay.

Commercial

Usage metric and reports aligned to the contracted billing definition.

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.