AdminConsole
Solution architect

From a real-world outcome to a buildable Mappls system

Choose an operating scenario and target runtime. The architect composes the smallest explicit product stack, separates request/response work from durable state, and links every build step to quickstarts, contracts, journeys, source evidence, and tested apps.

Compose your plan Open plan JSON
Use-case firstPlatform exactState-model explicitSource groundedRunnable evidence
Plan inputs

Tell us where value meets runtime

Leave product scope on “scenario default” unless you are deliberately reducing the entitlement boundary.

Shareable URL · deterministic output
Optional product boundary

Unchecked uses the complete scenario stack. Check products only to create a narrower plan.

Logistics · Web

A delivery promise customers can trust on Web

Fewer failed deliveries and a live, explainable ETA from checkout to doorstep.

Products
4
Contracts
71
Journeys
11
State model
hybrid
Operating scenario

The system has to survive the real world

At 18:05 a customer places a same-evening grocery order to a loosely formatted apartment address. The promise engine has eight minutes to validate serviceability and a two-hour window; dispatch must combine it with 37 stops, the driver may lose connectivity, and support needs one explainable timeline when the entrance is hard to find.

  1. 01

    Normalize the destination and retain its Mappls Pin

  2. 02

    Optimize stops against capacity and time windows

  3. 03

    Navigate with live rerouting

  4. 04

    Stream driver and order state

  5. 05

    Capture geotagged proof and reconcile exceptions

Product composition

Every capability has a delivery boundary

“Direct” means the product names the target platform. “Trusted server” keeps the product behind a REST boundary. “Entitlement dependent” requires a confirmed private distribution.

directstateless

Search & Places

Autosuggest, geocoding, nearby discovery, place details, and Mappls Pin addressing.

Autosuggest and text searchForward and reverse geocodingNearby and route-corridor search
trusted serverhybrid

Routes & Navigation

Routes, matrices, optimization, map matching, predictive ETAs, and turn-by-turn navigation.

Multi-profile routing and alternativesDistance and time matricesTrip and vehicle-route optimization
directstateful

InTouch Telematics

Live tracking, trips, devices, vehicles, events, geofences, and fleet intelligence.

Device and vehicle provisioningLive location and historical trailsTrips, stoppages, and events
entitlement dependenthybrid

Capture & Feedback

On-demand location capture, camera evidence, map feedback, and update workflows.

Single-shot and subscribed locationAccuracy and timeout policiesCamera and field evidence
Stateless lane18 contracts

Bounded request/response work that can be retried only under the operation's documented idempotency and timeout rules.

search-placesroutes-navigationcapture-feedback
Durable lane11 journeys · 53 contracts

Business aggregates and provider resources that survive a request, retain versioned evidence, and reconcile unknown outcomes.

routes-navigationintouch-telematicscapture-feedback
First implementation

Start at the exact runtime boundary

Web · 15 minutes

Render one accessible web map

a responsive map and text-synchronized selected place

public source
REST · 15 minutes

Your first trusted Mappls request

a validated autosuggest result from a credential-safe server boundary

public source
Six release gates

A plan that ends in evidence, not a demo

  1. 01

    Prove the contract

    A versioned source manifest naming every guide, package, host, auth generation, region, entitlement, and unresolved owner decision.

  2. 02

    Establish identity

    Application-owned business IDs mapped separately to Mappls Pins, provider resource IDs, request IDs, and aggregate versions.

  3. 03

    Ship the stateless slice

    One narrow request/response path with validation, timeouts, redaction, provenance, quota measurement, and useful denied/unavailable states.

  4. 04

    Own durable journeys

    Explicit states, commands, idempotency, optimistic versions, event/receipt time, reconciliation, human decisions, audit, and outbox behavior.

  5. 05

    Exercise the real journey

    A scenario test from entry through terminal outcome using the linked tutorial and downloadable reference application as evidence—not as a live-provider substitute.

  6. 06

    Release with evidence

    Entitlement conformance, privacy review, accessibility, performance, security, observability, support, rollback, and named product-owner approval.

Learning and runnable proof

Move from tutorial to complete journey

Durable journeys

Connected fleet trip6 states · 7 transitions
Fleet geofence exception6 states · 5 transitions
Coordinated incident response7 states · 8 transitions
Recoverable navigation session6 states · 6 transitions
Durable multi-stop itinerary6 states · 9 transitions
Consented address verification9 states · 11 transitions
iOS direction planning and navigation handoff8 states · 8 transitions
iOS geofence draft and publication boundary6 states · 6 transitions
iOS feedback report and review9 states · 9 transitions
Consent-bound location capture evidence8 states · 9 transitions
Governed place contribution and publication7 states · 8 transitions
Contract and source manifest

Inspect the evidence before installation

71 matching contracts16 matching guides
normalized contractsSearch & Places8 exact operations

Exact normalized operations are linked below; account contract and entitlement still require validation.

normalized contractsRoutes & Navigation11 exact operations

Exact normalized operations are linked below; account contract and entitlement still require validation.

normalized contractsInTouch Telematics53 exact operations

Exact normalized operations are linked below; account contract and entitlement still require validation.

reference onlyCapture & Feedback0 exact operations

No exact normalized REST operation is present in the captured contract corpus for this product. Use its source guides, SDK/widget/distribution surface, and entitlement process without substituting an adjacent API.

Featured operations

GET
AutoSuggest APIsearch-places · legacy-source · stateless · 853e2a51f94c
GET
Routing APIroutes-navigation · legacy-source · stateless · efefba560f22
GET
Gets the details of a single tripintouch-telematics · legacy-source · stateful · f475d06cfb9d
GET
Geocode APIsearch-places · legacy-source · stateless · b1ce0d03e440
GET
Route Optimization APIroutes-navigation · legacy-source · stateless · af458e128aba
GET
This API will get all the trips for a user.intouch-telematics · legacy-source · stateful · f475d06cfb9d
GET
Reverse Geocode APIsearch-places · legacy-source · stateless · fe7746feeb13
GET
Routing API with driving profileroutes-navigation · legacy-source · stateless · 5134fc7e305a
GET
Gets the live data of devices.intouch-telematics · legacy-source · stateful · 54637441ab0c
GET
Nearby APIsearch-places · legacy-source · stateless · 4819a31c609c
GET
Routing API with trucking profileroutes-navigation · legacy-source · stateless · 268532986484
GET
Gets the historical location events of a device.intouch-telematics · legacy-source · stateful · e12f19aca91a

Source guides

REST API
MAPPLS AI / ML APIscurrent · 80cfbc9b9c7c
SDK
Mappls Insight Embeddable Visualizationscurrent · 0ae2cda7c0a9
REST API
Mappls Intouch REST Apiscurrent · 06df37d758e9
REST API
Mappls Map APIs (REST) !current · a27fe1435b9c
Guide
Mappls Web Maps JScurrent · 5b7bd5c66a78
Widget
Mappls Web Pluginscurrent · 0500ead3cc1d
Guide
Sign up for Mapplscurrent · 6d102a2fe3c3
REST API
Skydnn AI APIscurrent · f407d95bd8b3
Sample
Angular Sample for MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Websample · 4280593e3c2f
Sample
MapmyIndia Interactive Maps JS SDK & MapmyIndia RESTful APIs for Web in Pure JSsample · 7648d4727442
Production truth

The generated plan is a starting boundary, not entitlement proof

  • Confirm current packages, hosts, auth generation, quota, region, and terms with the issued account.
  • Keep server credentials and privileged exchanges outside browser, mobile, embedded, and model context.
  • Preserve provider identity, source fingerprint, event time, receipt time, and business aggregate version.
  • Make permission denial, offline operation, timeout, quota, cancellation, and teardown complete product states.
  • Require attributable approval for dispatch, access, closure, evidence decisions, and destructive changes.
  • Run the release path on representative devices, networks, data volumes, and regional entitlements.
Copy this plan URLMachine-readable JSON