Work order management
A work order in Deepomatic corresponds to the set of elementary tasks that must be performed by a field worker.
A task in this context refers to a specific checkpoint that can be validated via the Deepomatic application. Tasks are grouped into task groups, which we can consider as a type of photo requested from the field workers. The list of task groups therefore corresponds to the list of photos that a field worker must take during an intervention.
Here you can find the different endpoints to create, update and delete work orders. Open each card to learn more.
post
https://api.{site-id}.customers.deepomatic.com
/v0.2/work-orders/
Create a new work order
curl 'https://api.{site-id}.customers.deepomatic.com/v0.2/work-orders/' \
-X POST \
-H 'Authorization: Token <your_api_key>' \
-H 'Content-Type: application/json' \
-d '{
"name": "work-order",
"metadata": {
"region": "North",
"intervention_date": "05-29-2023"
},
"tags": ["group-1", "group-2"],
"field_engineer_email": "[email protected]",
"work_order_types": ["one-equipment", "maintenance"]
}'
patch
https://api.{site-id}.customers.deepomatic.com
/v0.2/work-orders/{id}/
Update a work order
curl 'https://api.{site-id}.customers.deepomatic.com/v0.2/work-orders/{id}/' \
-X PATCH \
-H 'Authorization: Token <your_api_key>' \
-H 'Content-Type: application/json' \
-d '{"field_engineer_email": "[email protected]"}'
delete
https://api.{site-id}.customers.deepomatic.com
/v0.2/work-orders/{id}/
Delete a work order
curl 'https://api.{site-id}.customers.deepomatic.com/v0.2/work-orders/{id}/' \
-X DELETE \
-H 'Authorization: Token <your_api_key>' \
-H 'Content-Type: application/json'
Last modified 1mo ago