Less travel and better traceability for inspection, inputs, harvest, and compliance.
A cooperative must inspect hundreds of plots before monsoon planting, route teams across poor connectivity, track shared equipment, capture geotagged observations under farmer consent, prevent reports from being assigned to the wrong parcel, and compare issue recurrence without exposing precise farm data broadly.
Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.
Owns farmer relationship, parcel identity, consent, crop/season and authorized users; geometry versions are governed spatial assets.
Parcel ↔ stable ID, geometry version, CRS, farmer consent and season
GETGet all the activities done by devices w.r.t various geofences/geofence/activityThis 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 accuracy and candidate parcels, require field-worker confirmation or review, and never snap silently.
Creates plot-specific work and inspection requirements, skills, windows, inputs and equipment eligibility.
Task ↔ parcel/version, policy, assignee/equipment, offline command IDs
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 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Reject stale actor/version commands on sync, retain evidence and route it to an accountable reconciliation queue.
Mobile tasks, map packages, ordered commands and evidence manifests survive connectivity gaps with stable idempotency and versions.
Observation ↔ evidence hash, accuracy, event/receipt time, source and reviewer
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.
Scope events to authorized device/time/operation assignments and prevent cross-farm projections at the data boundary.
InTouch device observations derive utilization and exceptions by event time without replacing operator or maintenance records.
Analysis ↔ input versions, parameters, agronomist decision and audience policy
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.
Retain accuracy and candidate parcels, require field-worker confirmation or review, and never snap silently.
Joins exact parcel/evidence/weather/input versions, applies access controls and produces coarse shared insights with lineage.
Parcel ↔ stable ID, geometry version, CRS, farmer consent and season
GETTo get form based check in/out details/reports/forms/{formId}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 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Reject stale actor/version commands on sync, retain evidence and route it to an accountable reconciliation queue.
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.
/tasksGETGet all the activities done by devices w.r.t various geofences/geofence/activityGETTo get the task details for the given task id./tasks/{taskId}GETGets All The Configured Geofence(s)/geofence/GETGet users attendance details with travelled distance./reports/attendancesGETGet A Single Or Multiple Geofence(s)./geofence/{id}GETTo get form based check in/out details/reports/forms/{formId}GETGet all the activities done by devices w.r.t various geofences/geofences/activitiesGETGet users movement details/reports/movements/{userId}GETGets All The Configured Geofence(s)/geofencesPOSTTo create new Task/tasksGETGet A Single Or Multiple Geofence(s)./geofences/{id}Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.
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.