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, or
keys — 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	Excludes `sub_selection_options` from option payloads to reduce response size.
`ticket_field_ids`	String	No	Comma-separated list of ticket field IDs. Required if `keys` is not provided.
`ticket_field_keys`	String	No	Comma-separated list of ticket field keys. Required if `ids` is not provided.
`creator`	Boolean	No	If true, displays the `creator_user_id` and `creator_app_name` properties. If the ticket field is created by an app, `creator_app_name` is the name of the app and `creator_user_id` is `-1`. If the ticket field is not created by an app, then `creator_app_name` is null

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.

All third party trademarks (including logos and icons) are the property of their respective owners, which do not sponsor, authorize, or endorse this website.

Pricing Templates Integrations Blog Contact Us Help

Terms of Service Privacy Policy