Higher first-time-fix rates and auditable work from dispatch through customer sign-off.
A utility receives a no-power complaint for a commercial unit. Dispatch must resolve the service point, choose a technician with the correct certification and inventory, survive an offline basement visit, collect readings and imagery, route weak proof to review, and close the job only after the provider and customer records agree.
Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.
Owns customer/service asset, SLA, required skills, inventory, commercial outcome, and the authoritative terminal status.
Work order ↔ service asset/location ID, SLA, skill and inventory requirements
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 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Use optimistic aggregate versions and one active assignment invariant; surface conflict instead of last-write-wins.
Search, asset layers, and mGIS context bind the request to a stable service location, access notes, network assets, and hazards.
Assignment ↔ technician eligibility snapshot, ETA evidence, policy version
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.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Validate actor, task version, and transition preconditions for every queued command; retain rejected evidence.
Provider task identity mirrors explicit create, assign, accept, travel, arrive, prove, review/rework, and close transitions through an outbox/callback boundary.
Offline command ↔ stable idempotency key, expected aggregate version, device time
GETTo get the task details for the given task id./tasks/{taskId}This 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.
Move to named review/rework with reason and a new submission identity; never overwrite the rejected attempt.
Mobile guidance, offline command queue, checklists, evidence capture, and conflict UI operate under scoped task and consent policy.
Proof ↔ immutable submission ID/hash, consent, accuracy, checklist, reviewer decision
GETGet users attendance details with travelled distance./reports/attendancesThis 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.
Use optimistic aggregate versions and one active assignment invariant; surface conflict instead of last-write-wins.
Owned exception/review queues, audit, repeat-fault spatial analysis, and SLA metrics derive from immutable task/evidence history.
Work order ↔ service asset/location ID, SLA, skill and inventory requirements
POSTTo create new Task/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 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Validate actor, task version, and transition preconditions for every queued command; retain rejected evidence.
The recipe starts from the normalized GET /tasks contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://workmate.mapmyindia.com/apis/tasks?startTime=1700000000000&endTime=1700000000000&ownerId=1&assigneeId=1&clientDetails=true&activityDetails=truecurl --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.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
Every aggregate has an invariant, expected version, stable command identity, and attributable actor.
Duplicate, late, reordered, invalid, stale, timed-out, and restarted execution preserve one durable truth.
Unknown provider outcomes reconcile by original identity before replay or compensation.
Terminal decisions, human review, audit, outbox delivery, privacy, retention, and rollback remain independently evidenced.
/tasksGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETTo get the task details for the given task id./tasks/{taskId}GETRouting API with driving profile/{REST_KEY}/{resources}/driving/{geopositions}GETTo get the task list details./taskListsGETRouting API with trucking profile/{REST_KEY}/{resources}/trucking/{geopositions}POSTTo create new Task/tasksGETRouting API with biking profile/{REST_KEY}/{resources}/biking/{geopositions}PUTTo update the task description & status./tasks/{taskId}GETRouting API with walking profile/{REST_KEY}/{resources}/walking/{geopositions}GETGet users attendance details with travelled distance./reports/attendancesGETDistance Matrix Predictive ETA API/{REST_KEY}/distance_matrix_predictive/driving/{coordinates}Correlate 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.