Shorter pickup times with fewer calls, cancellations, and unsafe rendezvous points.
At a busy railway station, a rider searches for the station name but the legal vehicle pickup point is 420 metres away. The marketplace must suggest a safe entrance, match a driver by road ETA rather than straight-line distance, guide both parties, and preserve a reviewable record if either disputes arrival.
Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.
Owns request, fare, rider/driver identities, eligibility, assignment, cancellation, safety state, and settlement.
Ride request ↔ accepted pickup/drop Mappls Pins and selection revisions
GETAutoSuggest API/api/places/search/jsonThis 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.Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Present signed pickup zones/entrances as candidates and require explicit rider confirmation before matching.
Autosuggest and map confirmation resolve human text and viewport context to a precise Mappls Pin with entrance/landmark explanation.
Driver candidate ↔ capability, availability, position freshness, matrix ETA
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.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Exclude it from ETA ranking, show marketplace capacity honestly, and request fresh evidence rather than extrapolating indefinitely.
A bounded matrix ranks eligible fresh driver positions; marketplace policy adds workload, vehicle, safety, and deterministic tie-breaks.
Assignment ↔ aggregate version, chosen explanation, provider route revision
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.Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Retain both event streams, accuracy, call/support actions, and apply a versioned human-review policy.
Route revisions and event-time vehicle observations derive progress, rerouting, pickup-zone entry, and freshness.
Arrival evidence ↔ event/receipt time, accuracy, zone policy, rider/driver acknowledgement
GETRouting API with driving profile/{REST_KEY}/{resources}/driving/{geopositions}This normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Present signed pickup zones/entrances as candidates and require explicit rider confirmation before matching.
Rider and driver receive the same stable pickup identity with role-appropriate directions and a support-visible discrepancy trail.
Ride request ↔ accepted pickup/drop Mappls Pins and selection revisions
GETGets the list of all the nearby devices./devices/nearbyThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Exclude it from ETA ranking, show marketplace capacity honestly, and request fresh evidence rather than extrapolating indefinitely.
The recipe starts from the normalized GET /{REST_KEY}/still_image contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://apis.mapmyindia.com/advancedmaps/v1/${MAPPLS_REST_KEY}/still_image?center=28.5959394%2C77.2255611&zoom=15&size=400x400&ssf=1&markers=28.5959394%2C77.2255611&markers_icon=https%3A%2F%2Fimg.icons8.com%2Fmaterial-outlined%2F96%2F000000%2Ftruck.pngcurl --request GET \
--url "https://apis.mapmyindia.com/advancedmaps/v1/${MAPPLS_REST_KEY}/still_image?center=28.5959394%2C77.2255611&zoom=15&size=400x400&ssf=1&markers=28.5959394%2C77.2255611&markers_icon=https%3A%2F%2Fimg.icons8.com%2Fmaterial-outlined%2F96%2F000000%2Ftruck.png" \
--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.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
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.
/{REST_KEY}/still_imageGETNearby API/api/places/nearby/jsonGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETGets the list of all the nearby devices./devices/nearbyGETElevation API/{REST_KEY}/elevationGETAutoSuggest API/api/places/search/jsonGETRouting API with driving profile/{REST_KEY}/{resources}/driving/{geopositions}GETGets the live data of devices./devicePOSTTraveled Route Image API/{REST_KEY}/still_image_polylineGETGeocode API/api/places/geocodeGETRouting API with trucking profile/{REST_KEY}/{resources}/trucking/{geopositions}GETGets the historical location events of a device./devices/{deviceId}/eventsConfirm the correct receiving entrance, assign eligible transport, preserve courier custody, review condition exceptions, and reconcile receiver acceptance without retaining patient or clinical data.
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.