Get queue workflows
Use this request to get queue workflows and their associated issue types.
GET
https://api.tracker.yandex.net/v3/queues/{queue_ID}/workflows
Query format
Before making a request, get permission to access the API.
To get queue workflows, use an HTTP GET request.
GET /v3/queues/{queue_ID}/workflows
Host: api.tracker.yandex.net
Authorization: OAuth API_TOKEN
X-Org-ID or X-Cloud-Org-ID: ORGANIZATION_ID
Headers
-
Host: address of the node that provides the API. -
Authorization: Authorization token about these formats:-
OAuth OAUTH_TOKEN: For authorization using the OAuth 2.0 protocol. Learn more -
Bearer IAM_TOKEN: For authorization using an IAMÂ token, if a Yandex Identity Hub organization is linked to Tracker. Learn more
-
-
ID types
X-Org-IDorX-Cloud-Org-ID: Organization ID.-
Use the
X-Org-IDheader if a Tracker organization is linked to Yandex 360 for Business. -
Use the
X-Cloud-Org-IDheader if a Tracker organization is linked to Yandex Identity Hub.
Finding the ID
To get the organization ID, go to Administration → Organizations and copy the value from the ID field.
-
Resource
| Parameter | Description | Data type |
|---|---|---|
queue_ID |
Queue ID or key. The key is case-sensitive. | String or number |
Response format
If the request is successful, the API returns a response with code 200 OK.
The response body contains a JSON object. Its keys are workflow IDs, and its values are arrays of issue types associated with each workflow.
{
"dev": [
{
"self": "https://api.tracker.yandex.net/v3/issuetypes/1",
"id": "1",
"key": "task",
"display": "Issue"
}
]
}
Issue type parameters
| Parameter | Description | Data type |
|---|---|---|
| self | Link to the issue type. | String |
| id | Issue type ID. | String |
| key | Issue type key. | String |
| display | Issue type name displayed. | String |