request response35–50 min2 stages8 code languages

Contract slice: A living operations map for the city

One governed view from daily operations to infrastructure investment planning.

The real-world moment

A city receives reports of waterlogging, failed streetlights and waste overflow across different channels. It needs one governed map without collapsing department ownership, must deduplicate related reports, dispatch the correct crew, preserve citizen privacy, publish honest status, and analyze service equity using versioned ward and asset data.

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 directWorkmatestateful directInTouch Telematicsstateful directMapsstateless

Normalized operation coverage

An adjacent API is never substituted when the captured corpus has no exact contract.

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.Workmate13 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.Maps3 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.

Department systems of record

Catalog authoritative layers

Retain authoritative assets, work orders, ownership and service outcomes; the map does not become an ungoverned replacement master.

Stage operation

Layer ↔ steward, source, schema, CRS, sensitivity, version

GETStill Map Image API/{REST_KEY}/still_imageThis 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 departments claim the same incident

Keep one coordinating incident with explicit owning/participating work orders; never transfer authority by map edit alone.

Spatial data catalogue

Ingest live assets and citizen reports

mGIS registers layers, schemas, CRS, stewards, update cadence, license/sensitivity and immutable versions.

Stage operation

Report/alarm ↔ source identity, consent, event/receipt time, coarse/public projection

GETGets the live data of devices./deviceThis 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 drillCitizen report contains precise personal data

Restrict raw evidence, derive a coarse operational/public location and apply purpose-specific retention/redaction.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /tasks 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://workmate.mapmyindia.com/apis/tasks?startTime=1700000000000&endTime=1700000000000&ownerId=1&assigneeId=1&clientDetails=true&activityDetails=true

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://workmate.mapmyindia.com/apis/tasks?startTime=1700000000000&endTime=1700000000000&ownerId=1&assigneeId=1&clientDetails=true&activityDetails=true' \
  --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

GETTo get the list of tasks and their details/tasksGETGets the live data of devices./deviceGETStill Map Image API/{REST_KEY}/still_imageGETTo get the task details for the given task id./tasks/{taskId}

Progressive tutorials

AdvancedConsume Mappls events exactly once in effect55 min AdvancedQualify an iOS Mappls release2 hr

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.