---
metadata:
  - name: generator
    content: Diplodoc Platform v5.63.0
alternate:
  - https://yandex.com.tr/support/tracker/en/api/queues/get-triggers.md
  - href: https://yandex.com.tr/support/tracker/en/api/queues/get-triggers.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.com.tr/support/tracker/en/llms.txt
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt

# Get a list of queue triggers

The request allows you to get a list of all triggers created in the queue, with pagination support.

<div class="request_example yfm-code-floating-container method_get">
    <p>GET</p>
    <pre><code>https://api.tracker.yandex.net/v3/queues/<queue_id>/triggers</code></pre>
    <button class="yfm-clipboard-button"><svg width="16" height="16" viewBox="0 0 24 24" class="yfm-clipboard-icon" data-animation="15">
    <path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path>
    <path stroke="currentColor" fill="transparent" strokewidth="1.5" d="M9.5 13l3 3l5 -5" visibility="hidden">
        <animate id="visibileAnimation-15" attributeName="visibility" from="hidden" to="visible" dur="0.2s" fill="freeze" begin=""></animate>
        <animate id="hideAnimation-15" attributeName="visibility" from="visible" to="hidden" dur="1s" begin="visibileAnimation-15.end+1" fill="freeze"></animate>
    </path>
</svg>
</button>
</div>

<!-- source: en/api/_assets/style/methods.md -->

<!-- endsource: en/api/_assets/style/methods.md -->

## Request format {#query}

Before making the request, [get access to the API](https://yandex.com.tr/support/tracker/en/api/access.md).

To get a list of queue triggers, use an HTTP request with the `GET` method.

```json translate=no
GET /v3/queues/<queue_id>/triggers
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth-token>
X-Org-ID or X-Cloud-Org-ID: ORGANIZATION_ID
```

<!-- source: en/api/_includes/headings-no-body.md -->
{% cut "Headers" %}

* `Host`: address of the node that provides the API.

* <!-- source: en/api/_includes/authorization.md -->
  `Authorization`: Authorization token about these formats:

    - `OAuth OAUTH_TOKEN`: For authorization using the OAuth 2.0 protocol. [Learn more](https://yandex.com.tr/support/tracker/en/api/access.md#about_OAuth)

    - `Bearer IAM_TOKEN`: For authorization using an IAM token, if a Yandex Identity Hub organization is linked to Tracker. [Learn more](https://yandex.com.tr/support/tracker/en/api/access.md#iam-token)
  <!-- endsource: en/api/_includes/authorization.md -->


* <!-- source: en/api/_includes/org-id.md -->
  # ID types {#types}


  `X-Org-ID` or `X-Cloud-Org-ID`: Organization ID.

  - Use the `X-Org-ID` header if a Tracker organization is linked to Yandex 360 for Business.

  - Use the `X-Cloud-Org-ID` header if a Tracker organization is linked to Yandex Identity Hub.


  # Finding the ID {#find-id}


  To get the organization ID, go to **Administration** → [**Organizations**](https://tracker.yandex.com/admin/orgs) and copy the value from the **ID** field.
  <!-- endsource: en/api/_includes/org-id.md -->


{% endcut %}
<!-- endsource: en/api/_includes/headings-no-body.md -->

{% cut "Resource" %}

Parameter | Description | Data type
----- | ----- | -----
\<queue_id\> | Queue ID or key. The queue key is case-sensitive. | String or number

{% endcut %}

{% cut "Request parameters" %}

**Additional parameters**

Parameter | Description | Data type
-------- | -------- | ----------
perPage | Number of triggers per page. | Integer
id | ID of the last trigger from the previous page. Used to get the next page. | Number

{% endcut %}

## Pagination mechanism {#pagination}

The request uses relative pagination:

- Results are sorted by trigger ID in ascending order.
- To get the next page, use the ID of the last trigger from the previous page in the `id` parameter.

### Example of sequential requests {#pagination-example}

1. First request:
   ```
   GET /v3/queues/DESIGN/triggers?perPage=20
   ```

2. Next request:
   ```
   GET /v3/queues/DESIGN/triggers?perPage=20&id=<id_of_last_trigger>
   ```

## Response format {#answer}

{% list tabs %}

- Request completed successfully

  <!-- source: en/api/_includes/answer-200.md -->
  If the request is successful, the API returns a response with code `200 OK`.
  <!-- endsource: en/api/_includes/answer-200.md -->

  The response body contains information about the triggers in JSON format.

    ```json translate=no
    [
        {
            "id": 16,
            "self": "https://api.tracker.yandex.net/v3/queues/DESIGN/triggers/16",
            "queue": {
                "self": "https://api.tracker.yandex.net/v3/queues/DESIGN",
                "id": "26",
                "key": "DESIGN",
                "display": "Design"
            },
            "name": "trigger_name",
            "order": "0.0002",
            "actions": [
                {
                    "type": "Transition",
                    "id": 1,
                    "status": {
                        "self": "https://api.tracker.yandex.net/v3/statuses/2",
                        "id": "2",
                        "key": "needInfo",
                        "display": "Need Info"
                    }
                }
            ],
            "conditions": [
                {
                    "type": "Or",
                    "conditions": [
                        {
                            "type": "Event.comment-create"
                        }
                    ]
                }
            ],
            "version": 1,
            "active": true
        }
    ]
   ```

   {% cut "Response parameters" %}

   Parameter | Description | Data type
   ----- | ----- | -----
   id | Trigger ID. | Number
   self | Link to the trigger. | String
   [queue](#queue) | Queue where the trigger is created. | Can be specified as an object, as a string (if the [queue key](*queuekey) is passed), or as a number (if the queue ID is passed).
   name | Trigger name. | String
   order | Trigger weight. The parameter affects the display order of the trigger in the interface. | String
   [actions](#actions) | Array with trigger actions. | Array of objects
   [conditions](#conditions) | Array with trigger conditions. | Array of objects
   version | Trigger version. Each trigger change increments the version number. | Number
   active | Trigger status. Possible values:<ul><li>`true`— active;</li><li>`false`— inactive.</li></ul> | Boolean

   **Fields of the** `queue` **object** {#queue}

   <!-- source: en/api/_includes/queue.md -->
   | Parameter | Description | Data type |
   ----- | ----- | -----
   | self | Address of the API resource with information about the queue. | String |
   | id | Queue ID. | String |
   | key | Queue key. | String |
   | display | Queue name displayed. | String |
   <!-- endsource: en/api/_includes/queue.md -->

   **Fields of the** `actions` **array objects** {#actions}

   Parameter | Description | Data type
   ----- | ----- | -----
   type | Action type. Possible values:<ul><li>`Transition`— change the issue status;</li><li>`Update`— change field values;</li><li>`Move`— move the issue;</li><li>`Event.comment-create`— add a comment;</li><li>`CreateChecklist`— create a checklist;</li><li>`Webhook`— send an HTTP request;</li><li>`CalculateFormula`— calculate a value;</li><li>`Event.create`— create an issue.</li></ul>| String
   id | Action ID. | String
   [status](#status) | Issue status. | String

   **Fields of the** `conditions` **array objects** {#conditions}

   Parameter | Description | Data type
   ----- | ----- | -----
   type | Condition type. Possible values:<ul><li>`or`— logical OR;</li><li>`and`— logical AND.</li></ul> | String
   conditions | Array with trigger conditions.<br/>A condition has the `type` parameter — the condition type. Possible values:<ul><li>`CommentNoneMatchCondition`— the comment does not contain any of the fragments;</li><li>`CommentStringNotMatchCondition`— the comment does not contain the fragment;</li><li>`CommentFullyMatchCondition`— the comment matches;</li><li>`CommentAnyMatchCondition`— the comment contains any of the fragments;</li><li>`CommentStringMatchCondition`— the comment contains the fragment;</li><li>`CommentAuthorNot`— the comment author is not;</li><li>`CommentAuthor`— the comment author is;</li><li>`CommentMessageExternal`— comment type `Email`;</li><li>`CommentMessageInternal`— comment type `Comment in Tracker`.</li></ul>   |  Array of objects

   **Fields of the** `status` **array objects** {#status}

   <!-- source: en/api/_includes/status.md -->
   | Parameter | Description | Data type |
   ----- | ----- | -----
   | self | Address of the API resource with information about the status. | String |
   | id | Status ID. | String |
   | key | Status key. | String |
   | display | Status name displayed. | String |
   <!-- endsource: en/api/_includes/status.md -->

   {% endcut %}

- Request completed with an error

    If the request wasn't processed successfully, the response message contains information about the errors that occurred:

    <!-- source: en/api/_includes/answer-error-400.md -->
    400
    :   One or more request parameters have an invalid value.
    <!-- endsource: en/api/_includes/answer-error-400.md -->

    <!-- source: en/api/_includes/answer-error-403.md -->
    403
    :   You are not authorized to perform this action. You can check what rights you have in the Tracker interface. The same rights are required to perform an action via the API and interface.
    <!-- endsource: en/api/_includes/answer-error-403.md -->

    <!-- source: en/api/_includes/answer-error-404.md -->
    404
    :   The requested object was not found. You may have specified an invalid object ID or key.
    <!-- endsource: en/api/_includes/answer-error-404.md -->

    <!-- source: en/api/_includes/answer-error-422.md -->
    422
    :   JSON validation error, the request is rejected.
    <!-- endsource: en/api/_includes/answer-error-422.md -->

    <!-- source: en/api/_includes/answer-error-500.md -->
    500
    :   Internal service error. Try again later.
    <!-- endsource: en/api/_includes/answer-error-500.md -->

    <!-- source: en/api/_includes/answer-error-503.md -->
    503
    :   The API service is temporarily unavailable.
    <!-- endsource: en/api/_includes/answer-error-503.md -->

{% endlist %}

[*queuekey]: A queue key is a unique code for a queue consisting of Latin characters, for example `TEST`. The key is contained in the link to the queue and its issues, and you need to specify it in API requests and auto action settings. You can't change the key after creating the queue.