Reply to an existing work order message by its message_id. Supports asynchronous processing via async=true.
access_token OAuth 2.0 Access Token
In: query
Work Order ID
ID of work order message
Asynchronous
true | falseActing user id
application/json
add message request body.
Reply message content
Whether to send a classic alert notification
Whether the problem was reopened with this reply
curl -X POST "https://api-sandbox.fndev.net/api/rest/v2/workorders/0/messages/0" \ -H "Content-Type: application/json" \ -d '{ "message": "Please proceed with the installation.", "classic_alert": true }'{
"actions": [],
"correlation_id": "string_value",
"metadata": {
"total": 100,
"page": 0,
"pages": 5,
"per_page": 20,
"columns": "string_value",
"view": "string_value",
"sort": "string_value",
"order": "string_value"
},
"params": [],
"f_work_order": [],
"fs_work_order": true,
"f_only_workorder": true,
"fs_only_workorder": true,
"results": []
}{
"status": 500,
"message": "Operation successful."
}{
"status": 500,
"message": "Operation successful."
}{
"status": 500,
"message": "Operation successful."
}application/json
application/json
application/json
application/json
Last updated on
curl -X POST "https://api-sandbox.fndev.net/api/rest/v2/workorders/0/messages/0" \
-H "Content-Type: application/json" \
-d '{
"message": "Please proceed with the installation.",
"classic_alert": true
}'