durable operation2–3 hr5 stages8 code languages

Operating journey: Route coordinated response under pressure

Reduced time to scene and safer decisions across dispatch, responders, and command.

The real-world moment

A caller reports a road collision near an informal landmark while multiple units are returning from other incidents. The control room must resolve location confidence, choose capable available responders using fresh positions and vehicle-aware ETA, update routes around hazards, prevent double dispatch, prove arrival, and replay the incident for review.

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

directSearch & Placesstateless directRoutes & Navigationhybrid directInTouch Telematicsstateful directGIS & Analyticshybrid

Normalized operation coverage

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

Search & Places8 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Routes & Navigation11 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.GIS & Analytics0 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.

CAD incident record

Resolve location from address, pin, or device

Owns call, incident identity, priority, location revisions, assigned resources, hazards, resolution and review.

Stage operation

Incident location ↔ revision, source, confidence, confirmer

GETAutoSuggest API/api/places/search/jsonThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.

Evidence to retain

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

Failure drillCaller description produces multiple locations

Show ranked candidates and confidence to the call taker; record confirmation and every revision.

Location resolution

Find eligible nearby responders

Combines address, landmark, Mappls Pin and consented device evidence while retaining candidates, confidence and human confirmation.

Supporting operation

Unit eligibility ↔ capability, availability, jurisdiction, telemetry freshness

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 drillUnit position is stale

Exclude from automated ranking or mark ETA unavailable; request fresh evidence and let an accountable dispatcher decide.

Resource and route service

Route with vehicle constraints

Filters capability/availability/jurisdiction first, then uses matrix/route evidence with freshness and deterministic dispatch policy.

Stage operation

Dispatch ↔ matrix evidence, route revision, expected aggregate versions

GETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}This normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.

Evidence to retain

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

Failure drillHazard changes after dispatch

Append a hazard revision, compute a new route identity, notify assigned units and retain both plans.

Live coordination

Track units and changing hazards

Ingests event-time unit telemetry and hazard revisions, derives progress and arrival evidence, and blocks one unit from two active incidents.

Supporting operation

Arrival/resolution ↔ objective evidence, actor, times, open-hazard/exception checks

GETGets the list of all the nearby devices./devices/nearbyThis 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 drillCaller description produces multiple locations

Show ranked candidates and confidence to the call taker; record confirmation and every revision.

Command and review

Replay the incident for review

Role-specific views, immutable actions, communication references, late evidence and outcome metrics support command and after-action review.

Supporting operation

Incident location ↔ revision, source, confidence, confirmer

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 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillUnit position is stale

Exclude from automated ranking or mark ETA unavailable; request fresh evidence and let an accountable dispatcher decide.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /api/places/search/json contract. Execute six deterministic fixture outcomes before an issued account is involved.

Local request composerCode stays local · fixtures are explicit

GETRequest inputs

7 editable · 1 protected

queryrequiredqueryEnter the query on which the search has to be done.locationqueryLocation is required to get location biased autosuggest results.regionqueryIt takes in the country code. Possible values are listed in a table here. Default is India (IND).podqueryIt takes in the place type code which helps in restricting the results to certain chosen type. This optional parameter & its related effect on response is not applicable for regions apart from India (IND). Below mentioned are the codes for the pod: SLC: Sublocality LC: Locality CITY: City VLG: Village SDIST: Subdistrict DIST: District STATE: State SSLC: SubsublocalityfilterqueryThis parameter helps you restrict the result either by mentioning a bounded area or to certain eloc (6 digit code to any poi, locality, city, etc.). This optional parameter & its related effect on response is not applicable for regions apart from India (IND). Below mentioned are the available types: filter = pin:It takes pincode/postal code of an area{e.g. filter=pin:110055} filter = bounds lat1,lng1;lat2,lng2(latitude,longitude){e.g. filter=bounds 28.598882, 77.212407; 28.467375, 77.353513} filter = cop {eloc} (string) {e.g. filter=cop:YMCZ0J}bridgequery(Valueless)It initiates a bridge to be created to provide applicable nearby API searches in the suggestedSearches response object. This optional parameter & its related effect on response is not applicable for regions apart from India (IND).hyperLocalquery(valueless): This parameter lets the search give results that are hyper-localized to the reference location passed in the location parameter. This means that nearby results are given higher ranking than results far from the reference location. Highly prominent results will still appear in the search results, however they will be lower in the list of results. This parameter will work ONLY in conjunction with the location parameter. This optional parameter & its related effect on response is not applicable for regions apart from India (IND).

Generated in eight languages

Environment-backed credentials

GET

https://atlas.mapmyindia.com/api/places/search/json?query=mapmyindia&location=28.612964%2C77.229463&region=IND&pod=CITY&filter=pin%3A110001&bridge=true&hyperLocal=true

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://atlas.mapmyindia.com/api/places/search/json?query=mapmyindia&location=28.612964%2C77.229463&region=IND&pod=CITY&filter=pin%3A110001&bridge=true&hyperLocal=true' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"

Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN 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