Viewing trigger logs
Use this request to get HTTP request action logs for the specified trigger.
GET
https://api.tracker.yandex.net/v3/queues/<queue_key>/triggers/<trigger_ID>/webhooks/log
Note
By default, the request returns only the last 10 log entries. To get more entries, use the limit parameter.
Request format
Before sending a request, get permission to access the API.
To get the logs, use an HTTP GET request:
GET /v3/queues/<queue_key>/triggers/<trigger_ID>/webhooks/log
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth_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 Cloud Organization organization is linked to Tracker. Learn more
-
-
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 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_key> | Queue ID or key. The queue key is case-sensitive. | String or number. |
| <trigger_ID> | Trigger ID | String |
Request parameters
Additional parameters
| Parameter | Description | Data type |
|---|---|---|
| issueId | ID of the issue where the trigger was activated. | String |
| limit | Number of log entries in the response. The default value is 10. The maximum value is 100. Example: limit=100 |
Number |
| from | Start of the log filter time range in YYYY-MM-DDThh:mm:ss.sss±hhmm format. |
String |
| to | End of the log filter time range in YYYY-MM-DDThh:mm:ss.sss±hhmm format. |
String |
Example 1: Getting the last 100 log entries for a specific issue
- An HTTP GET method is used.
- A request is sent for a trigger from the
DEVqueue.- The trigger ID is 6.
- The issue ID is
DEV-123. The response will only contain logs linked to this issue.- Set the maximum number of log entries in the response.
GET /v3/queues/DEV/triggers/6/webhooks/log?issueId=DEV-123&limit=100 Host: api.tracker.yandex.net Authorization: OAuth <OAuth_token> X-Org-ID or X-Cloud-Org-ID: <organization_ID>
Example 2: Getting log entries over a certain period
- An HTTP GET method is used.
- A request is sent for a trigger from the
DEVqueue.- The trigger ID is 6.
- Set the time range: September 23, 2025, from 00:00 to 23:59.
GET /v3/queues/DEV/triggers/6/webhooks/log?from=2025-09-23T00:00:00&to=2025-09-23T23:59:59 Host: api.tracker.yandex.net Authorization: OAuth <OAuth_token> X-Org-ID or X-Cloud-Org-ID: <organization_ID>
Response format
If the request is successful, the API returns a response with code 200 OK.
The response body contains the results in JSON format.
[
{
"startTime": "2025-02-25T14:22:03.596+0000",
"endTime": "2025-02-25T14:22:03.831+0000",
"duration": 235,
"triggerId": 123***,
"actionId": 1,
"issueId": "66f682f13f442b**********",
"request": {
"method": "POST",
"endpoint": "https://api.telegram.org/bot123*******:AAHCATQsN**********/sendMessage",
"headers": {
"X-Startrek-Transport": "vNCc******/aRh5**********",
"Content-Type": "PSb4IkZm+OemrDmVvPX0h4uFOP8sKid9vp**********"
},
"body": "{\n\"chat_id\":\"-4116*****\",\n\"parse_mode\":\"markdown\",\n\"text\":\"Hello!\"\n}",
"webhookAuthContext": {
"type": "noauth"
}
},
"response": {
"headers": {
"Access-Control-Expose-Headers": "XXX",
"Strict-Transport-Security": "XXX",
"Server": "XXX",
"Access-Control-Allow-Origin": "XXX",
"Access-Control-Allow-Methods": "XXX",
"X-Ya-Instance": "XXX",
"Connection": "XXX",
"Content-Length": "XXX",
"Date": "XXX",
"Content-Type": "XXX"
},
"statusCode": 200
},
"id": "67bdd20b604a9c**********"
}
]
Response parameters
| Parameter | Description | Data type |
|---|---|---|
| startTime | Trigger activation start time in YYYY-MM-DDThh:mm:ss.sss±hhmm format. |
String |
| endTime | Trigger activation end time in YYYY-MM-DDThh:mm:ss.sss±hhmm format. |
String |
| duration | Trigger activation duration in milliseconds. | String |
| triggerId | Trigger ID | String |
| actionId | Trigger action ID. | String |
| issueId | ID of the issue where the trigger was activated. | String |
| request | Object with information about the parameters of the sent HTTP request. | Object |
| response | Object with information about the parameters of the received response. | Object |
| id | Trigger activation ID. | String |
request object fields
| Parameter | Description | Data type |
|---|---|---|
| method | HTTP request method. | String |
| endpoint | URL of the resource where the HTTP request was sent to. | String |
| headers | HTTP request headers. | Object |
| body | HTTP request body. | String |
| webhookAuthContext | Object with information about the request authorization method. | Object |
webhookAuthContext object fields
| Parameter | Description | Data type |
|---|---|---|
| type | Authorization method. | String |
response object fields
| Parameter | Description | Data type |
|---|---|---|
| headers | Response headers. | Object |
| statusCode | HTTP request status code. | Number |
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.