Errors Explorer
Query and filter errors from the Error Explorer.
Returns aggregated error metrics for a project within a date range, with optional filters for error target, message, category, action, tags, branches, authors, and groups.
Get aggregated error metrics for a project within a date range. Supports filtering by error_target, error_message, error_category, error_action, test_title, tags, branches, authors, and groups.
An organization API key, sent as Authorization: Bearer <key>. A key carries one scope for the whole API: a read key reaches the GET endpoints, a write key reaches all of them. A crnts_pat_ personal access token is accepted as a Bearer while its owner remains an eligible administrator in its active organization. Each operation requires the corresponding scope stored on that token.
The project ID
proj_abc123Start date in ISO 8601 format
2024-01-01T00:00:00.000ZEnd date in ISO 8601 format
2024-01-31T23:59:59.999ZPage number (0-indexed)
0Maximum number of results (1-100)
50Filter by tags (can be specified multiple times using bracket notation, e.g., tags[]=value1&tags[]=value2)
["tag1","tag2"]Logical operator for tags filter: OR (match any) or AND (match all). Default: OR.
ORPossible values: Filter by groups (can be specified multiple times using bracket notation, e.g., groups[]=group1&groups[]=group2)
["group1","group2"]Filter by git authors (can be specified multiple times using bracket notation, e.g., authors[]=author1&authors[]=author2)
["author1","author2"]Filter by error target (e.g. CSS selector, URL)
Filter by error message (case-insensitive partial match)
Filter by error category
Filter by error action
Filter by test title (case-insensitive partial match)
Field to order results by
countPossible values: Sort direction: desc (default) or asc.
descPossible values: Metric used for timeline ranking (occurrence, test, or branch)
occurrencePossible values: Maximum number of top errors per timeline bucket (1-50). Default: 5.
5Successful response
Invalid request parameters
Authentication failed
The credential authenticated but is not permitted to use this endpoint. Five refusals share the status: a read API key on an endpoint that writes, an OAuth token that was not granted the scope the endpoint needs (insufficient_scope), an OAuth token that was granted it but whose holder no longer has a role permitting it (insufficient_role), an OAuth token on an endpoint that accepts an API key and nothing else (api_key_required), and an API key on an endpoint that answers for a user (user_credential_required). Discriminate on code rather than on the message, which is free-form. The first refusal predates the codes and sets none. Only insufficient_scope carries the challenge header, because it is the only one a client can act on by re-authorizing.
Resource not found
GET /v1/errors/{projectId}?date_start=2026-01-01T00%3A00%3A00.000Z&date_end=2026-01-01T00%3A00%3A00.000Z HTTP/1.1
Host: api.currents.dev
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"status": "OK",
"data": {
"list": [
{
"message": "text",
"error_category": "text",
"error_action": "text",
"error_target": "text",
"signature": "text",
"title": "text",
"spec": "text",
"count": 1,
"details": {
"tests": {
"count": 1
},
"branches": {
"count": 1
}
}
}
],
"timeline": [
{
"date": "text",
"count": 1,
"items": [
{
"message": "text",
"error_category": "text",
"error_action": "text",
"error_target": "text",
"signature": "text",
"title": "text",
"spec": "text",
"count": 1,
"details": {
"tests": {
"count": 1
},
"branches": {
"count": 1
}
}
}
]
}
],
"count": 1,
"total": 1,
"nextPage": 1
}
}Last updated
Was this helpful?