AdminConsole
Recipes/Travel/stateless
request response35–50 min2 stages8 code languages

Contract slice: Turn inspiration into an itinerary

More confident trip planning and higher conversion from discovery to booking.

The real-world moment

A family planning a three-day city break saves attractions from editorial stories, nearby search and partner inventory. The product must preserve place identity across languages and sources, sequence a feasible itinerary, show neighbourhood and RealView context, avoid stale opening assumptions, and hand off to booking/navigation without losing the selected place.

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
01
Travel content and inventory

Discover places by theme and proximity

Own editorial collections, commercial availability, pricing, disclosures and booking outcome while mapping every item to a stable place identity.

Stage operation

Travel item ↔ Mappls Pin, editorial/partner IDs, language and provenance

GETNearby API/api/places/nearby/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 drillTwo sources describe the same attraction

Reconcile through stable place identity and retain source-specific content/availability rather than merging by name.

02
Place discovery

Build a time-aware itinerary

Search/nearby and curated sources resolve to Mappls Pins with provenance, language/display labels and duplicate reconciliation.

Supporting operation

Itinerary ↔ ordered stable IDs, constraints, version and route revision

GETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}This 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 drillOpening or availability data is stale

Show source/time, confirm with the authoritative partner and avoid routing a day as guaranteed feasible.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

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

Local request composerCode stays local · fixtures are explicit
GETRequest inputs
4 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://atlas.mapmyindia.com/api/places/textsearch/json?query=Where+is+Lajpat+Nagar&region=IND&location=28.612964%2C77.229463&filter=pin%3A110020
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/textsearch/json?query=Where+is+Lajpat+Nagar&region=IND&location=28.612964%2C77.229463&filter=pin%3A110020' \
  --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.

Maintained capstone

Store Locator

Discover eligible branches, compare distance and ETA, preserve Mappls Pin identity, and hand off safely to navigation.

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.