request response35–50 min2 stages8 code languages

Contract slice: Coordinate time-critical care without losing custody

Shorter transfer and specimen journeys with fewer missed hand-offs and a complete chain of operational custody.

The real-world moment

A district hospital needs to transfer a patient to a tertiary campus while a laboratory specimen travels separately under a strict stability window. The coordinator must resolve the correct clinical entrance, choose eligible transport, retain custody at every hand-off, detect route and temperature delay, reveal only the minimum operational location, and close each journey only after the receiving team accepts it.

Operating contract

Make ownership visible before code.

Prove one bounded contract, identity handoff, failure response, and observable first success.

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

Capability map

directSearch & Placesstateless directRoutes & Navigationhybrid directInTouch Telematicsstateful entitlement-dependentCapture & Feedbackhybrid 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.Capture & Feedback0 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.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.

Clinical and laboratory systems

Resolve the correct facility, campus, and entrance

Authoritative systems own patient or specimen identity, clinical priority, consent, custody policy, stability window and receiving acceptance; the location workflow stores only opaque operational references.

Supporting operation

Transfer ↔ opaque clinical reference, priority, consent and accepted entrance

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

Failure drillSearch selects the public entrance instead of emergency receiving

Present approved campus entrances as explicit candidates, require coordinator confirmation, and retain the original query and selection revision.

Facility and entrance resolution

Select an eligible vehicle and bounded route

Search and governed campus data resolve a stable Mappls Pin or enterprise entrance identity while preserving candidate, confirmer and revision evidence.

Stage operation

Transport assignment ↔ eligibility snapshot, vehicle, route revision and expiry

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

Failure drillLocation or condition evidence becomes stale

Show last verified time and source, alert the responsible coordinator, and stop projecting an invented ETA or safe-condition claim.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

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

Local request composerCode stays local · fixtures are explicit

GETRequest inputs

6 editable · 0 protected

regionquery'It takes in the country code. Possible values are listed in a table here. Default is India (IND).'addressrequiredqueryaddress to be geocodeditemCountqueryparameter can be set to get maximum number of result items from the API (default: 1).biasqueryThis parameter can be used to set Urban or Rural bias. A positive value sets the Urban bias and a negative value sets Rural bias. This optional parameter & its related effect on response is not applicable for regions apart from India (IND). Allowed values are: 0 : Default: (No bias) -1 : Rural 1 : UrbanpodFilterqueryThis parameter can be used to set admin level restriction. The result will be either the given admin level or equivalent admin or higher in the hierarchy. No lower admin will be considered for geocoding.This optional parameter & its related effect on response is not applicable for regions apart from India (IND). Allowed values are: hno : house number hna : house name poi : point of interest street : street sslc : sub sub locality village : village slc : sub locality sdist : sub district loc : locality city : city dist : district pincode :pincode state : stateboundqueryThis parameter can be used to set admin boundary, which means geocoding will be done within the given admin. The allowed admin bounds are Sub-District, District, City, State and Pincode. The parameter accepts the admin eLoc as value. This optional parameter & its related effect on response is not applicable for regions apart from India (IND). Note: Please note that podFilter & bound parameters are mutually exclusive. They cannot be used together in an API call.

Generated in eight languages

Environment-backed credentials

GET

https://atlas.mapmyindia.com/api/places/geocode?region=ind&address=237+Okhla+industrial+estate+phase+3+new+delhi%2C+delhi+110020&itemCount=1&bias=0&podFilter=example&bound=TAVI5S

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/geocode?region=ind&address=237+Okhla+industrial+estate+phase+3+new+delhi%2C+delhi+110020&itemCount=1&bias=0&podFilter=example&bound=TAVI5S' \
  --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.

Bound inputs and outputsAbortable timeoutRetry only safe readsTyped empty and denied statesSafe request correlationCredential and URL-log redaction

Definition of done

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.

Continue with canonical evidence

Contracts, tutorials, and journeys stay linked.

Contract set

GETGeocode API/api/places/geocodeGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETGets The List Of Alarm Config(s)/alarm/alarmLog/GETNearby API/api/places/nearby/json

Progressive tutorials

AdvancedQualify an iOS Mappls release2 hr AdvancedQualify React Native native parity100 min

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.