GET /api/v2/ticket_fields/show_many
Returns multiple ticket fields in a single request.
Provide either:
ids— a comma-separated list of ticket field IDs, orkeys— a comma-separated list of ticket field keys
Up to 100 values are accepted.
The response payload matches the List Ticket Fields response format.
Sideloads
The following sideloads are supported:
| Name | Will sideload |
|---|---|
| users | The user or users that created fields |
Allowed For
- Anyone
Servers
- https://{subdomain}.{domain}.com
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
exclude_sub_selection_options |
Boolean | No |
If true, excludes sub-selection options from dropdown fields in the response. |
keys |
String | No |
Comma-separated list of ticket field keys to retrieve. Up to 100 values accepted. Use field keys like 'priority', 'status', 'subject' instead of numeric IDs. Either |
ids |
String | No |
Comma-separated list of ticket field IDs to retrieve. Up to 100 values accepted. Either |
creator |
Boolean | No |
If true, includes creator information in the response. |
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.