Appearance

List Ticket status ​

Endpoint ​

http
GET /unified/ticketing/ticket_status
Integrations supported
  • Accelo
  • Azure DevOps
  • Basecamp
  • Bitbucket
  • Dixa
  • Freshdesk
  • FuseDesk
  • GitLab
  • Happyfox
  • Help Scout
  • HubSpot
  • Jira
  • Jira Service Management
  • Kustomer
  • Linear
  • LiveAgent
  • Monday.com
  • Productboard
  • Qualtrics CoreXM
  • Re:amaze
  • Shortcut
  • SolarWinds Service Desk
  • SurveySparrow Ticket Management
  • Trello
  • Trengo
  • YouTrack
  • Zendesk

Query parameters ​

Refer Specifying query parameters in Truto APIs

integrated_account_id
string · uuid
REQUIRED · 

The ID of the integrated account to use for the request.

Example: 62f44730-dd91-461e-bd6a-aedd9e0ad79d
truto_response_format
string

The format of the response.

  • unified returns the response with unified mappings applied.
  • raw returns the unprocessed, raw response from the remote API.
  • normalized applies the unified mappings and returns the data in a normalized format.
  • stream returns the response as a stream, which is ideal for transmitting large datasets, files, or binary data. Using streaming mode helps to efficiently handle large payloads or real-time data flows without requiring the entire data to be buffered in memory.

Defaults to unified.

All possible enum values:
  • unified
  • raw
  • normalized
  • stream
Example: unified
truto_key_by
string

By default the result attribute is an array of objects. This parameter allows you to specify a field in each result objects to use as key, which transforms the result array into an object with the array items keyed by the field. This is useful for when you want to use the result as a lookup table.

Example: id
truto_ignore_limit
boolean

Ignores the limit query parameter.

truto_ignore_remote_data
boolean

Excludes the remote_data attribute from the response.

truto_exclude_fields
array

Array of fields to exclude from the response.

Example: truto_exclude_fields[]=id&truto_exclude_fields[]=name
remote_query
object

Query parameters to pass to the underlying API without any transformations. Refer this guide to see how to structure the query parameters.

Example: remote_query[foo]=bar
collections
array

Collections associated with the ticket_status

Required in
  • Basecamp
  • HubSpot
ticket_type
object

Type of the ticket

Required in
  • Azure DevOps
id
string

The unique identifier for a ticket type

name
string

The name of the ticket type

workspace
object

Workspace associated with the ticket_status

Required in
  • Basecamp
  • Jira Service Management
id
string

The unique identifier for the workspace

Response Body ​

result
object[]

List of Ticket status

id
string
REQUIRED · 

The status's unique identifier

Supported in
  • Accelo
  • Azure DevOps
  • Basecamp
  • Freshdesk
  • Happyfox
  • HubSpot
  • Jira
  • Jira Service Management
  • Linear
  • Productboard
  • Qualtrics CoreXM
  • Shortcut
  • YouTrack
  • Zendesk
name
string

The status's name

Supported in
  • Accelo
  • Azure DevOps
  • Basecamp
  • Freshdesk
  • Happyfox
  • HubSpot
  • Jira
  • Jira Service Management
  • Linear
  • Productboard
  • Qualtrics CoreXM
  • Shortcut
  • YouTrack
  • Zendesk
description
string

The status's description

Supported in
  • Freshdesk
  • Jira
  • Jira Service Management
  • Zendesk
etag
string

The unique identifier for the specific version of the resource.

remote_data
object

Raw data returned from the remote API call.

next_cursor
string

The cursor to use for the next page of results. Pass this value as next_cursor in the query parameter in the next request to get the next page of results.