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.
Prove one bounded contract, identity handoff, failure response, and observable first success.
Owns request, fare, rider/driver identities, eligibility, assignment, cancellation, safety state, and settlement.
Ride request ↔ accepted pickup/drop Mappls Pins and selection revisions
GETNearby API/api/places/nearby/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
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.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.
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.
Valid, empty, invalid-input, authentication-denied, rate-limited, timed-out, and unavailable outcomes are distinguishable.
The accepted Mappls or provider identity is retained separately from display text and coordinates.
Credentials remain in the approved runtime and logs retain only safe request evidence.
The exact source contract, auth generation, host, entitlement, quota, and region are reviewed before live traffic.
/{REST_KEY}/still_imageGETNearby API/api/places/nearby/jsonGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETGets the list of all the nearby devices./devices/nearbyConfirm 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.