Faster, safer restoration with an explainable view of affected assets, customers, crews, and residual risk.
A monsoon storm trips feeders across two districts while flood exposure changes road access by the minute. Grid operations must correlate alarms against an exact network version, estimate affected service points, obtain an independently approved switching plan, dispatch capable crews, preserve every field observation, and avoid declaring restoration until telemetry and customer-impact evidence converge.
Compose multiple capabilities while the application owns user intent, policy, and continuity.
The utility system of record owns assets, connectivity, protection settings, switching authority and customer-service relationships; versioned mGIS layers add terrain, flood, access and vegetation context without replacing that authority.
Grid asset ↔ topology/configuration version, owner and safety class
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.Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Retain each source alarm, topology version and correlation reason; require operator correction and create a new incident revision rather than rewriting prior evidence.
Append-only alarms and calls map to exact network versions and form bounded incidents under a versioned correlation rule with operator correction.
Alarm ↔ source/event/content identity, event/receipt time and mapped asset
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.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Append the hazard revision, invalidate the route identity, keep the switching plan separate, and require dispatch to approve a safe replacement.
An application-owned plan separates electrical safety approval from skill-, equipment- and ETA-aware Workmate assignments; no map or route result authorizes switching.
Switching plan ↔ exact assets, sequence, approver, version and expiry
GETTo get the list of tasks and their details/tasksThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Keep the task evidence complete but the outage in reconciliation; query authoritative device and customer-impact sources before closure.
Offline-safe tasks, route evidence, asset identity, observations and proof submissions preserve stable command IDs, expected versions and event/receipt time.
Crew task ↔ eligibility snapshot, route evidence, provider identity and proof
GETTo get the list of tasks and their details/tasksThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Retain each source alarm, topology version and correlation reason; require operator correction and create a new incident revision rather than rewriting prior evidence.
The recipe starts from the normalized GET /alarm/alarmLog/ contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000curl --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.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
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.
/alarm/alarmLog/GETTo get the list of tasks and their details/tasksGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETThis API will get all the alarm configurations for a user./alarmGETTo get all your client details/clientsGETDistance Matrix Predictive ETA API/{REST_KEY}/distance_matrix_predictive/driving/{coordinates}GETGets The List Of Alarm Config(s)/alarms/alarmlogs/GETTo get the list of client category in an account/configurations/categoriesCorrelate an outage, govern independent switching approval, dispatch an assigned crew, preserve rework, and reconcile restoration from telemetry and customer-impact evidence.
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.