request response35–50 min2 stages8 code languages

Contract slice: Move material safely across a changing mine

Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses.

The real-world moment

A blast changes the active pit and closes a ramp midway through a shift. Dispatch must publish the newly approved road and exclusion-zone version, reassign compatible trucks and loaders, guide offline-capable cycles, distinguish telemetry delay from a stopped vehicle, preserve safety interventions, and reconcile production only from accepted load and dump evidence.

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 directInTouch Telematicsstateful directWorkmatestateful entitlement-dependentOffline & Automotivestateful entitlement-dependentCapture & Feedbackhybrid

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

Mine plan and safety authority

Publish the approved pit, road, and exclusion-zone version

The mine system of record owns surveyed geometry, blast areas, geotechnical restrictions, road classes, equipment compatibility and operating authorization.

Supporting operation

Mine map package ↔ survey/version, region, signature, compatibility and approval

GETGets The List Of Alarm Config(s)/alarm/alarmLog/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 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillA truck wakes with the previous pit map

Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.

Versioned offline map release

Assign compatible equipment and operators

Approved pit, road, zone and configuration manifests move through signed dual-slot qualification and rollback before vehicles activate them.

Supporting operation

Assignment ↔ equipment/operator capability, shift, plan version and expected aggregate version

GETTo get the list of tasks and their details/tasksThis 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 drillTelemetry silence looks like an idle vehicle

Separate freshness from motion state, show last verified evidence, and ask dispatch to reconcile rather than charging productive-time loss automatically.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /alarm/alarmLog/ 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

deviceIdqueryNot Mandatory field. This is the ID of the device for which the alarm log need to be fetched. You can pass single device ID or multiple device IDs separated by commaalarmTypequeryNot Mandatory field. This is the type of alarm for which the alarm log need to be fetched. You can pass single alarm type or multiple device IDs separated by comma. Type of alarm to create. Following are the alarm types & their corresponding IDs. IGNITION: 21, OVERSPEED: 22, UNPLUGGED: 23, PANIC: 24, GEOFENCE: 26, STOPPAGE: 27, IDLE: 28, TOWING: 29, GPRS CONNECTIVITY: 126, VEHICLE BATTERY: 129, MILEAGE: 133, GPS CONNECTIVITY: 146, DISTANCE COVERED: 151, INTERNAL BATTERY VOLTAGE:161startTimerequiredqueryMandatory field. This is start timestamp in secondsendTimerequiredqueryMandatory field. This is end timestamp in seconds

Generated in eight languages

Environment-backed credentials

GET

https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}"

Credential-safe by constructionSet MAPPLS_INTOUCH_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

GETGets The List Of Alarm Config(s)/alarm/alarmLog/GETTo get the list of tasks and their details/tasksGETThis API will get all the alarm configurations for a user./alarmGETTo get all your client details/clients

Progressive tutorials

AdvancedQualify an iOS Mappls release2 hr AdvancedConsume Mappls events exactly once in effect55 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.