request response35–50 min2 stages8 code languages

Contract slice: Choose the next store with evidence

Faster site screening and investment decisions grounded in a reusable spatial model.

The real-world moment

A retailer is comparing 60 candidate neighbourhoods for 12 stores. Analysts must combine travel-time catchments, competition, demographics, access and existing performance, explain every score, prevent data drift between committee meetings, and revoke a shared decision view after the acquisition window closes.

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

directGIS & Analyticshybrid directSearch & Placesstateless directMapsstateless

Enterprise data products

Publish candidate sites and performance data

Own approved store performance, candidate, demand, competition and financial datasets with source, license, observation date and steward.

Supporting operation

Dataset version ↔ source/license/date/schema/CRS/content hash

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.

Evidence to retain

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

Failure drillDemographic feed changes mid-analysis

Publish a new immutable input version and rerun; retain both result revisions and prevent silent replacement.

mGIS version registry

Generate drive-time catchments

Publishes immutable spatial dataset versions with content hash, schema, CRS, validation diagnostics and access policy.

Supporting operation

Catchment attempt ↔ route profile, threshold, input versions, engine version

GETText Search API/api/places/textsearch/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.

Evidence to retain

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

Failure drillCandidate geometry has the wrong CRS

Fail before processing with feature-level diagnostics and require a corrected dataset version.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

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

Local request composerCode stays local · fixtures are explicit

GETRequest inputs

10 editable · 0 protected

keywordsrequiredqueryEnter the query on which the search has to be done. Operators in Keywords parameter To send multiple keywords in a request, we’ve defined a couple of operators that can help the developers wrap their applications around this functionality. Below are the operators: The “ ; ” Operator: This operator is an “or” operator. Defining multiple keywords separated with a “ ; ” would provide results that satisfies either of the keywords. The “ $ ” Operator: This operator is a “and” operator. Defining multiple keywords separated with a “ $ ” would provide results that satisfy all the provided keywords. (default). To use these operators, simple just send in the keywords parameter like below: &keywords=corefLocationrequiredqueryProvides the location around which the search will be performed. e.g. refLocation=28.454,77.435. The refLocation parameter can also accept eLoc as reference location. This configuration is not active by default. Please contact MapmyIndia API support for further details. Example: refLocation=17ZUL7pagequeryprovides number of the page to provide results from.regionqueryit takes in the country code. LKA, IND, BTN, BGD, NPL for Sri-Lanka, India, Bhutan, Bangladesh, Nepal respectively. Default is India (IND)radiusqueryProvides the range of distance to search over (default 1000, min, 500, max, 10000)boundsquery(x1,y1;x2,y2) Allows the developer to send in map bounds to provide a nearby search of the geobounds. where x1,y1 are the lat lng of the bound. The bounds are set from topLeft to bottomRight (North-West to South-East).filterqueryIt uses key:value pair(s) to fine tune discovery of places by filtering the results. e.g. categoryCode:FODCOF valid IDs for key value pairs are: categoryCode: can take in category codes as inputsortByqueryProvides configured sorting operations for the client on cloud. Below are the available sorts: dist:asc & dist:desc - will sort data in order of distance from the passed location (default). name:asc & name:desc - will sort the data on alphabetically bases. imp - will sort data in order of decreasing prominence of the place.searchByqueryprovides configurable search operations for the client on cloud. Below are the available sorts: dist(default) - will sort data in order of distance from the passed location (default). imp - will search data in order of prominence of the place.podqueryIt takes in the place type code which helps in restricting the results to certain chosen type. Access to this parameter is controlled from the backend. This parameter, if provided will override any values provided in keywords request param. Below mentioned are the available values for pod: SLC - Sublocality LC - Locality CITY - City STATE - State

Generated in eight languages

Environment-backed credentials

GET

https://atlas.mapmyindia.com/api/places/nearby/json?keywords=FODCOF&refLocation=28.612964%2C77.229463&page=1&region=IND&radius=10000&bounds=28.639256%2C77.211133%3B28.625214%2C77.237483&filter=categoryCode%3AFODCOF&sortBy=dist%3Aasc&searchBy=dist&pod=LC

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/nearby/json?keywords=FODCOF&refLocation=28.612964%2C77.229463&page=1&region=IND&radius=10000&bounds=28.639256%2C77.211133%3B28.625214%2C77.237483&filter=categoryCode%3AFODCOF&sortBy=dist%3Aasc&searchBy=dist&pod=LC' \
  --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

GETNearby API/api/places/nearby/jsonGETStill Map Image API/{REST_KEY}/still_imageGETText Search API/api/places/textsearch/jsonGETElevation API/{REST_KEY}/elevation

Progressive tutorials

IntermediateShip a Mappls map in Cordova and Ionic50 min AdvancedQualify a Cordova location release80 min

Maintained capstone

Airside Turnaround Desk

Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.

Inspect 22 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.