composed experience90–120 min4 stages8 code languages

Application flow: 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.

Compose multiple capabilities while the application owns user intent, policy, and continuity.

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

Capability map

directSearch & Placesstateless directMapsstateless entitlement-dependentApp Widgets & Deep Linksstateless directRoutes & Navigationhybrid

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.Maps3 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.App Widgets & Deep Links0 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.Routes & Navigation11 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.

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

GETPlace Detail API/apis/O2O/entity/{eLoc}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 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.

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

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

Itinerary aggregate

Visualize routes and neighborhoods

Owns ordered saved place IDs, day/time constraints, route revisions, visits/skips, sharing and deliberate cancellation.

Stage operation

Place fact ↔ source and observation/freshness timestamp

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

Failure drillNavigation app is absent

Use an HTTPS fallback that preserves the destination and offers browser navigation or store choice without redirect loops.

Map and rich context

Embed 3D or RealView context

Renders routes, neighbourhoods, 3D/RealView or deep-linked experiences with accessible alternatives and explicit freshness.

Supporting operation

Hand-off ↔ destination/offer identity, safe campaign fields, fallback and observed stage

GETPlace Detail API/apis/O2O/entity/{eLoc}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 4 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.

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

Generated in eight languages

Environment-backed credentials

GET

https://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.

Application-owned intentStable cross-capability identityPartial-failure fallbackCancellation and teardownFreshness and provenanceQuota and latency budget

Definition of done

Every capability has one owner, bounded input, explicit timeout, and useful unavailable state.

Application intent survives refresh, back navigation, duplicate callbacks, and partial capability failure.

Provider identities, source fingerprints, request identities, and application decisions remain attributable.

Accessibility, privacy, quota, observability, support, and rollback evidence cover the complete user flow.

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.

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

Make ownership visible before code.

Edit once. Generate eight trusted-runtime implementations.

Break the journey before customers do.

Definition of done

Contracts, tutorials, and journeys stay linked.

Contract set

Progressive tutorials

Durable state machines

Store Locator