PUT /ticket_types/{ticket_type_id}/attributes/{id}
You can update an existing attribute for a ticket type.
Servers
- https://api.intercom.io
- https://api.eu.intercom.io
- https://api.au.intercom.io
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The unique identifier for the ticket type attribute which is given by Intercom. |
ticket_type_id |
String | Yes |
The unique identifier for the ticket type which is given by Intercom. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Intercom-Version |
String | No |
Possible values:
Default value: "2.12" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
name |
String | No |
The name of the ticket type attribute |
description |
String | No |
The description of the attribute presented to the teammate or contact |
archived |
Boolean | No |
Whether the attribute should be archived and not shown during creation of the ticket (it will still be present on previously created tickets) |
visible_on_create |
Boolean | No |
Whether the attribute is visible to teammates when creating a ticket in Inbox. Default value: true |
visible_to_contacts |
Boolean | No |
Whether the attribute is visible to contacts when creating a ticket in Messenger. Default value: true |
list_items |
String | No |
A comma delimited list of items for the attribute value (only applicable to list attributes) |
required_to_create |
Boolean | No |
Whether the attribute is required to be filled in when teammates are creating the ticket in Inbox. Default value: false |
multiline |
Boolean | No |
Whether the attribute allows multiple lines of text (only applicable to string attributes) |
required_to_create_for_contacts |
Boolean | No |
Whether the attribute is required to be filled in when contacts are creating the ticket in Messenger. Default value: false |
allow_multiple_values |
Boolean | No |
Whether the attribute allows multiple files to be attached to it (only applicable to file attributes) |
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.