Retrieve an Organization's Events Count by Project

Go to Product

Query summarized event counts by project for your Organization. Also see for reference.


Organization Slug
The slug of the organization the resource belongs to.

the sum(quantity) field is bytes for attachments, and all others the 'event' count for those types of events.

sum(times_seen) sums the number of times an event has been seen. For 'normal' event types, this will be equal to sum(quantity) for now. For sessions, quantity will sum the total number of events seen in a session, while times_seen will be the unique number of sessions. and for attachments, times_seen will be the total number of attachments, while quantity will be the total sum of attachment bytes.

  • sum(quantity) - sum(quantity)
  • sum(times_seen) - sum(times_seen)
Stats Period (*)

This defines the range of the time series, relative to now. The range is given in a <number><unit> format. For example 1d for a one day range. Possible units are m for minutes, h for hours, d for days and w for weeks.You must either provide a statsPeriod, or a start and end.

Interval (*)

This is the resolution of the time series, given in the same format as statsPeriod. The default resolution is 1h and the minimum resolution is currently restricted to 1h as well. Intervals larger than 1d are not supported, and the interval has to cleanly divide one day.

Start (*)

This defines the start of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with end instead of statsPeriod.

End (*)

This defines the inclusive end of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with start instead of statsPeriod.

Project (*)
The ID of the projects to filter by.
Category (*)

If filtering by attachments, you cannot filter by any other category due to quantity values becoming nonsensical (combining bytes and event counts).

If filtering by error, it will automatically add default and security as we currently roll those two categories into error for displaying.

  • error - error
  • transaction - transaction
  • attachment - attachment
  • replays - replays
  • profiles - profiles
Outcome (*)

See for more information on outcome statuses.

  • accepted - accepted
  • filtered - filtered
  • rate_limited - rate_limited
  • invalid - invalid
  • abuse - abuse
  • client_discard - client_discard
Reason (*)
The reason field will contain why an event was filtered/dropped.
Download (*)
Download the API response in as a csv file
Result Format
Specify how the response should be mapped to the table output. The following formats are available:
  • Structured Table: Returns a parsed table with data split into rows and columns.
    • Start:
    • End:
    • Projects:
  • Raw Response: Returns the raw response in a single row with the following columns:
    • body: Response body
    • status: HTTP status code

Input Ports

Configuration data.

Output Ports

Result of the request depending on the selected Result Format.
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found


This node has no views


  • No workflows found



You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.