Versioning
Contract and schema compatibility, release notes, deprecation and model-year support.
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.
Mappls Auto supports different ownership models without treating them as disconnected products.
Create a synthetic OEM project, inspect effective rights, issue one-time sandbox identity and evaluate production evidence.
Explore path →02Call search, route, tracking, analytics and workflow services from OEM cloud or applications.
Explore path →03Trace all 33 products through 20 vehicle, cockpit, cloud, app, content and operations contracts.
Explore path →04Freeze eight coverage dimensions, seven lifecycle exits, nine verification domains, eight standards families and seven operational domains.
Explore path →05Review all eleven SaaS products, twenty-two contracts, degraded states, operations and production-release boundaries.
Explore path →06Build web, mobile, companion and cockpit experiences from Mappls map and navigation components.
Explore path →07Review APP-01 through APP-09 across Android, AAOS, iOS, TypeScript and responsive web, including offline and release boundaries.
Explore path →08Configure a complete Mappls-powered navigation, connected, fleet or mobility experience.
Explore path →09Integrate device-resident map content, navigation runtime, vehicle signals, eHorizon or edge devices.
Explore path →010Inspect all seven edge runtimes, their authority, resource bounds, degradation and cross-runtime release gate.
Explore path →011Review all six reference designs, software attachment, manufacturing evidence and EVT-to-SOP gates.
Explore path →012Trace all 33 products through twelve cross-program evidence and acceptance gates.
Explore path →013Exercise bounded probable paths, attribute validity, degradation, replay and a non-control safety boundary.
Explore path →014Validate precise intake, resource eligibility, provider-source state, closure evidence and reproducible network analytics.
Explore path →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.
# 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.
The full API page expands scope, common automotive uses and links into the official documentation.
Web, mobile and embedded maps with vector or raster tiles, styles, camera, markers, geometry, events, custom layers and 2D/3D presentation.
Open integration guide →Location-biased suggestions, place, address and POI matching with fuzzy, phrase and category behavior.
Open integration guide →Resolve text or structured addresses to coordinates, and coordinates to address, place and road context.
Open integration guide →Resolve, share and open compact location identities for deep-link and cross-device journeys.
Open integration guide →Discover POIs, chargers, parking, fuel, service and amenities near a point or route.
Open integration guide →Passenger, bike, truck, pedestrian and EV routing as entitled, including traffic, alternatives, toll, time and distance context.
Open integration guide →Many-to-many distance, duration and ETA for assignment, dispatch and optimization decisions.
Open integration guide →Sequence stops, orders, tasks and visits under distance, time, capacity and operational constraints.
Open integration guide →Each blueprint maps the product to contract families, adjacent interfaces, canonical context, delivery stages and release evidence—without inventing universal endpoints or availability.
One governed digital twin for every entitled vehicle journey.
Open blueprint →02 · SaaS & cloudTurn live vehicle state into an exception-led operating picture.
Open blueprint →03 · SaaS & cloudPlan fewer kilometres—and keep the plan useful when reality changes.
Open blueprint →04 · SaaS & cloudTreat automotive map content as a governed product lifecycle—not a file transfer.
Open blueprint →05 · SaaS & cloudConnect EV journey quality with charging-network decisions and field action.
Open blueprint →06 · SaaS & cloudPut assets, incidents, work and location intelligence on one operational map.
Open blueprint →07 · SaaS & cloudTurn vehicle truth and road context into an energy plan the driver can understand.
Open blueprint →08 · SaaS & cloudDeliver versioned road-ahead context with an explicit operational design boundary.
Open blueprint →09 · SaaS & cloudKeep rider promise, driver execution and fleet decision on one trip identity.
Open blueprint →10 · SaaS & cloudPut deterministic automotive policy between every model and every tool.
Open blueprint →11 · SaaS & cloudMake every integration environment, entitlement and release explainable.
Open blueprint →12 · Native applicationA resilient OEM cockpit built around one route truth.
Open blueprint →13 · Native applicationMake the OEM app useful before, during and after every drive.
Open blueprint →14 · Native applicationMake range explainable, routes energy-aware and charging actionable.
Open blueprint →15 · Native applicationJoin assignment, navigation, task state and support into one trustworthy mobile execution loop.
Open blueprint →16 · Native applicationAn operator workspace designed around action, not map clutter.
Open blueprint →17 · Native applicationBring precise location and live execution into high-stress ownership moments.
Open blueprint →18 · Native applicationA voice-and-touch assistant whose state never depends on model wording.
Open blueprint →19 · Native applicationMake the mobility promise clear from pickup search to completed trip.
Open blueprint →20 · Native applicationPut entitlement, trace and release evidence beside the code that needs it.
Open blueprint →21 · Embedded softwareA confidence-aware vehicle position that survives difficult roads and signals.
Open blueprint →22 · Embedded softwareThe route and guidance engine behind every entitled cockpit surface.
Open blueprint →23 · Embedded softwareMake vehicle state usable without coupling every product to every ECU contract.
Open blueprint →24 · Embedded softwarePreserve the right events through the wrong network conditions.
Open blueprint →25 · Embedded softwareActivate the right content on the right vehicle—and always know how to recover.
Open blueprint →26 · Embedded softwareOne secure lifecycle from factory identity to end-of-life.
Open blueprint →27 · Embedded softwareDeliver qualified road-ahead profiles with freshness, confidence and safe degradation.
Open blueprint →28 · Hardware systemAutomotive-grade identity, positioning and connectivity for the connected vehicle.
Open blueprint →29 · Hardware systemA field-resilient operational location device with a governed cloud lifecycle.
Open blueprint →30 · Hardware systemJoin road or cabin video to the vehicle event that explains why it matters.
Open blueprint →31 · Hardware systemAn integrated cockpit system designed around boot, navigation, vehicle and lifecycle reality.
Open blueprint →32 · Hardware systemGlanceable rider guidance that respects sunlight, gloves, vibration and attention.
Open blueprint →33 · Hardware systemA connected navigation-adjacent product with an explicit safety and battery boundary.
Open blueprint →A production integration specifies technical behavior, data rights, quality and operations—not only method names.
Contract and schema compatibility, release notes, deprecation and model-year support.
Availability, latency, rate, burst, timeout, retry, idempotency and failover.
Territory, version, update, freshness, attribution, caching and offline rights.
Taxonomy, deterministic fallback, confidence and provenance where applicable.
Request IDs, dashboards, logs, incident communication, test data and replay.
Usage metric and reports aligned to the contracted billing definition.
Choose the surfaces, modules, deployment and lifecycle that fit your next RFQ. We will turn it into a focused discovery brief.