How many events of a name happened in each hour or day of the workspace's timezone (timezone), to catch tracking that broke: a line that falls to zero after a release. Accepted events only; refused ones are in the event log (status=rejected) with the reason. from (inclusive) and to (exclusive) choose the window, a date meaning the start of that day in timezone; it runs from the bucket holding from to the one holding the moment before to, without gaps, at most 366 points. from must be before to. Events past retention are gone and not counted.
Query parameters
namestringrequired
The event name, exactly as it was tracked.
1–128 characters
intervalstringrequired
The bucket size.
one of hour, day
fromstringoptional
Inclusive: a date-time, or a date meaning the start of that day in the workspace timezone. The series starts with the bucket holding it. By default 30 days (day) or 24 hours (hour) before to.
tostringoptional
Exclusive, in the same forms: the series ends with the bucket holding the moment before it. Now by default.
Header parameters
Kirora-Workspacestringoptional
Partner keys only: the child workspace to act in, by the external id the partner gave it. Without it, a partner key acts in its own workspace. Any other key that sends it is refused with 403, and an unknown workspace is 404.
pattern ^[A-Za-z0-9._:-]{1,128}$
Returns
Returns 200 OK with an EventSeries in data. Otherwise returns an error; Errors lists every code and which to retry.
namestringrequired
intervalstringrequired
one of hour, day
timezonestringrequired
The workspace timezone the buckets follow.
pointsobject[]required
One point per bucket, oldest first and without gaps, at most 366.
at most 366 items
2 child attributes
startsAtstringrequired
When this hour or day starts in timezone, as an instant.
date-time
countintegerrequired
Accepted events that happened in it.
min 0
We'd like to use Google Analytics cookies to understand how people use this site. You can accept or decline them. See our Cookie Policy.