Get top active items

Response

{ "err": 0, "result": [ // each element in the list is an object with an "item" object and a "counts" list { // data describing the item (similar to that returned by GET /api/1/item/:id) "item": { "id": 2071, "counter": 1007, "environment": "production", "framework": 0, "last_occurrence_timestamp": 1728410581, "level": 40, "occurrences": 54, "project_id": 12345, "title": "Something went wrong", "unique_occurrences": 5 }, // list of occurrence counts in the past 24 hours. Oldest first. "counts": [12, 10, 7, 3, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 8, 5, 6] }, { /* more elements ... */ } ] }

By default, the sort of the top items is by the level of severity, then the number of occurrences. E.g. an item with a warning level and 300 occurrences will be below an item with an error level and 150 occurrences. This behavior can be changed by passing sort=occurrences in the query parameters, which will sort only by the number of occurrences in the time period.

Note that the level and framework are returned as integers here. 10, 20, 30, 40, and 50 representing the debug, info, warning, error, and critical levels, respectively. For the full integer-framework mapping, please see the Framework IDs section in our docs.

Log in to see full request history
Query Params
int32
Defaults to 24

Number of recent hours to consider. Min 1, max 168.

string

Comma-separated list of environments to consider. If empty, then returns results for "any environment".

string

To sort by occurrences only and not by item level, add sort=occurrences. This is the only accepted value for sort at this time, any other value will return an error.

Headers
string
required

Use a Project Access Token with 'read' scope

Response

Language
Click Try It! to start a request and see the response here! Or choose an example:
application/json