durable operation2–3 hr5 stages8 code languages

Operating journey: Navigation built for intermittent connectivity

Reliable guidance across coverage gaps without giving up traffic, search freshness, or safety.

The real-world moment

A vehicle crosses a long connectivity gap after receiving a regional data update the night before. Navigation must boot with a compatible signed offline package, plan and guide locally, blend online traffic/search when available, protect driver attention, and recover automatically if the new package or runtime is unhealthy.

Operating contract

Make ownership visible before code.

Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.

Application state: stateful
Planning calls: 0
Credentials accepted: No
Write authority: None

Capability map

entitlement-dependentOffline & Automotivestateful directRoutes & Navigationhybrid directSearch & Placesstateless directInTouch Telematicsstateful

Normalized operation coverage

An adjacent API is never substituted when the captured corpus has no exact contract.

Offline & Automotive0 exact · reference onlyNo 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.Routes & Navigation11 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Search & Places8 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.InTouch Telematics53 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.

Vehicle/OEM identity

Activate the head unit

Owns hardware, market/region, entitlement, runtime compatibility, privacy/consent, activation and update campaign.

Supporting operation

Vehicle manifest ↔ hardware/runtime/region/entitlement versions

GETGets the live data of devices./deviceThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillPower loss during update

Write only the inactive slot and switch one atomic pointer after verification; boot always finds a previously acknowledged package.

Dual-slot offline runtime

Install compatible signed regional data

Maintains one active and one staged signed package, atomic activation pointer, health acknowledgement and rollback evidence.

Supporting operation

Data package ↔ epoch, region, size, content/signature hash, compatibility

GETGeocode API/api/places/geocodeThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillOnline traffic disappears mid-route

Keep guiding from the last valid local route, mark traffic freshness and avoid blocking safety-critical guidance.

Local navigation

Plan and guide offline

Search index, routing graph, guidance and map rendering operate without network under pinned runtime/data/profile versions.

Supporting operation

Route session ↔ offline/online sources, profile, data/traffic versions

GETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}This is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillNew package boots but fails route smoke test

Fail health acknowledgement, restore the prior slot and upload privacy-safe diagnostics when connectivity returns.

Online enhancement

Blend online traffic and search when available

Trusted cloud boundary adds fresh search, traffic and telemetry only when entitled and available; responses carry freshness/provenance.

Supporting operation

Update event ↔ campaign, stage, evidence, event/receipt time, health/rollback outcome

GETGets the historical location events of a device./devices/{deviceId}/eventsThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillPower loss during update

Write only the inactive slot and switch one atomic pointer after verification; boot always finds a previously acknowledged package.

Fleet operations

Stage atomic map and runtime updates

Campaign, download, verification, activation, health, rollback and support diagnostics are stateful journeys with aggregate metrics.

Supporting operation

Vehicle manifest ↔ hardware/runtime/region/entitlement versions

GETGets drive details of a device./devices/drivesThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillOnline traffic disappears mid-route

Keep guiding from the last valid local route, mark traffic freshness and avoid blocking safety-critical guidance.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /{REST_KEY}/{resources}/{profile}/{geopositions} contract. Execute six deterministic fixture outcomes before an issued account is involved.

Local request composerCode stays local · fixtures are explicit

GETRequest inputs

12 editable · 1 protected

resourcesrequiredpathThe different resources available within MapmyIndia Routing API. These resources have their own individual allocations and not all are allocated for evalulations be default. For allocating particular resource on your API credentials, please contact apisupport@mapmyindia.com Table 1. Resources Element Value Description Resources routeadv to calculate a route & its duration without considering traffic conditions. routeeta to get the updated duration of a route considering live traffic; Applicable for India only “region=ind” and “rtype=1” is not supported. This is different from routetraffic ; this resource balances between a preferred path and aggressive traffic congestion avoidance. routetrafprofilerequiredpathThe different profiles available within MapmyIndia Routing API. These profiles have their own individual transport modes and not all are allocated for evalulations be default. For allocating particular profiles on your API credentials, please contact apisupport@mapmyindia.com Table 2. Profiles Element Value Description Profiles driving Meant for 4-wheeler/passenger car routing. biking Meant for two-wheeler routing. Routing with this profile is restricted to routeadv only. region & rtype request parameters are not supported in two-wheeler routing. walking Meant for pedestrian routing. Routing with this profile is restricted to routeadv only. region & rtype request parameters are not supportedgeopositionsrequiredpathgeopositions(part of URL) are either: pair of comma separated longitude & latitude values OR eLoc(s). First geoposition will be consider as start point (mandatory); a last geoposition will be considered as end point (mandatory) and those in between are via points (optional). {longitude1},{latitude1};{longitude2},{latitude2};eLoc1;eLoc2; ... (part of URL).geometriesqueryThis parameter used to change the route geometry format/density (influences overview and per step).rtypequerytype of route (integer) required for navigation, where values mean: 0 optimal (default) 1 shortest (it will calculate route by excluding access penalties like private roads, etc.)stepsqueryReturn route steps for each route leg. Possible values are true/false. By default it will be used as false.excludequeryAdditive list of road classes to avoid, order does not matter. Possible values are toll, motorway & ferry. Multiple values can be sent separated by comma.regionqueryThis parameter is optional for India; for other countries (such as Sri Lanka, Nepal, Bangladesh, Bhutan + many more) this parameter is mandatory. Possible values are listed in a table here.bearingsqueryLimits the search to segments with given bearing in degrees. The referencing will be to the true north and in clockwise direction. (Part of premium offering)alternativesquerySearch for alternative routes. Passing a number: e.g. alternatives=n searches for up to n alternative routes. Please note that even if alternative routes are requested, a result cannot be guaranteed.radiusesqueryLimits the search to given radius in meters. For all way-points including start and end points. {radius};{radius}[;{radius} ...]. (Part of premium offering)overviewqueryAdd overview geometry either full, simplified according to highest zoom level it could be display on, or not at all. Possible values are simplified (default), full , false . (Part of premium offering)

Generated in eight languages

Environment-backed credentials

GET

https://apis.mapmyindia.com/advancedmaps/v1/${MAPPLS_REST_KEY}/route_eta/driving/28.612964%2C77.229463?geometries=polyline&rtype=0&steps=true&exclude=ferry&region=IND&bearings=180&alternatives=2&radiuses=100%3B100&overview=simplified

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url "https://apis.mapmyindia.com/advancedmaps/v1/${MAPPLS_REST_KEY}/route_eta/driving/28.612964%2C77.229463?geometries=polyline&rtype=0&steps=true&exclude=ferry&region=IND&bearings=180&alternatives=2&radiuses=100%3B100&overview=simplified" \
  --header "Accept: application/json"

Credential-safe by constructionSet MAPPLS_REST_KEY only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Reliability contract

Break the journey before customers do.

These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.

Idempotent commandsOptimistic aggregate versionsEvent and receipt timeTransactional outboxUnknown-outcome reconciliationIndependent human decisionsRestart recoveryImmutable audit evidence

Definition of done

Every aggregate has an invariant, expected version, stable command identity, and attributable actor.

Duplicate, late, reordered, invalid, stale, timed-out, and restarted execution preserve one durable truth.

Unknown provider outcomes reconcile by original identity before replay or compensation.

Terminal decisions, human review, audit, outbox delivery, privacy, retention, and rollback remain independently evidenced.

Continue with canonical evidence

Contracts, tutorials, and journeys stay linked.

Maintained capstone

Care Transfer Desk

Confirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.

Inspect 17 verified tests Download full application

Source-grounded, not authority-granting

This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.

Make ownership visible before code.

Edit once. Generate eight trusted-runtime implementations.

Break the journey before customers do.

Definition of done

Contracts, tutorials, and journeys stay linked.

Contract set

Progressive tutorials

Durable state machines

Care Transfer Desk