API call to fill the mandatory fields and close a request simultaneously
The "Close Request" API call is used to close a request. But to fill the mandatory fields if any and close a request simultaneously, the "Update Request" API call can be utilized.
Example: To fill the mandatory fields like "Resolution" and "Priority" and to close the request.
Method: PUT
Input Data:
{
"request": {
"resolution": {
"content": "(any resolution content)"
},
"priority": {
"name": "(priority)",
},
"status": {
"name": "Closed"
},
"closure_info": {
"requester_ack_resolution": true,
"requester_ack_comments": "(any comment)",
"closure_comments": "(any comment)",
"closure_code": {
"name": "success"
}
}
}
}
New to ADSelfService Plus?
Related Articles
Close a request using API - Postman example
INPUT_DATA Value as follows {"operation": {"details": { "closeAccepted": "Accepted", "closeComment": "The closing comment" }}} PUT API example - ...Close the request upon adding a note.
Kindly follow the steps mentioned below: 1) Go to Admin >> Developer Space >> Custom Function >> Global Functions >> Copy & Paste the attached GF_Content.txt and save it with a name. Update the URL and technician key as per your instance. Refer to ...Script: Close associated changes when a request is closed
Use case: In many cases, the client never comes back to confirm the change. This means that the change remains opened indefinitely. When the ticket is closed it is logical that the change to be closed. No one is going to close a ticket unless the ...Reply a request through v3 API (Postman)
The API documentation for replying a request is under Admin > API Documentation > Request > Add notification Syntax of the URL: http(or https)://<servername>:<portnumber>/api/v3/requests/<Request ID>/notifications?TECHNICIAN_KEY=<API Key> Call: Post ...How to close linked requests when a parent request is closed.
This post describes the use of a python script to close all the linked request when a parent request is closed using custom triggers. Use Case: We get tickets which are getting reported for the same issue but different end-users so that once we ...