PUT /api/v2/triggers/update_many
Updates the position or the active status of multiple ticket triggers. Any additional properties are ignored.
Allowed For
- Agents
Request Parameters
The PUT request expects a triggers object that lists the ticket triggers to update.
Each ticket trigger may have the following properties:
| Name | Mandatory | Description |
|---|---|---|
| id | yes | The ID of the ticket trigger to update |
| position | no | The new position of the ticket trigger |
| active | no | The active status of the ticket trigger (true or false) |
| category_id | no | The ID of the new category the ticket trigger is to be moved to |
Example Request
{
"triggers": [
{"id": 25, "position": 3},
{"id": 23, "position": 5},
{"id": 27, "position": 9},
{"id": 22, "position": 7}
]
}
Servers
- https://{subdomain}.{domain}.com
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
triggers[] |
Array | No | |
triggers[].id |
Integer | Yes |
The ID of the ticket trigger to update |
triggers[].active |
Boolean | No |
The active status of the ticket trigger (true or false) |
triggers[].category_id |
String | No |
The ID of the new category the ticket trigger is to be moved to |
triggers[].position |
Integer | No |
The new position of the ticket trigger |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.