Removing a tag from a queue

Use this request to remove a tag from a queue.

POST

https://api.tracker.yandex.net/v3/queues/<queue_ID>/tags/_remove

Only the queue owner or administrator can remove a tag. Before removing a tag, make sure it is not used in any of the queue issues.

Query format

Before making a request, get permission to access the API.

To remove a tag, use an HTTP POST request. In the request body, specify the parameters in JSON format.

POST /v3/queues/<queue_ID>/tags/_remove
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth_token>
X-Org-ID or X-Cloud-Org-ID: <organization_ID>

{
    "tag": "<tag_name>"
}
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 Cloud Organization organization is linked to Tracker. Learn more

  • 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 Cloud Organization.

    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 queue key is case-sensitive. String or number
Request body parameters

Required parameters

Parameter Value Data type
tag Tag name String

Response format

If the request is successful, the API returns a response with code 204.

The response body is missing.

If the request is processed incorrectly, the API returns a response with an error code:

400
One or more request parameters have an invalid value.
401
The user is not authorized. Make sure that actions described in the API access section are performed.
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.
404
The requested object was not found. You may have specified an invalid object ID or key.
422
JSON validation error, the request is rejected.
Previous
Getting queue tags
Next
Grant queue access rights