List usage events
Read consumption events recorded against a module. Requires scope: usage:read.
Writing an event is a separate, publishable-key call (POST /usage/track) so a browser can meter. Reading them back is not — a client-side key must not be able to enumerate a workspace’s usage. Events are returned newest first and paged at 50 by default: a usage event is written per metered call in your own application, so this list is not bounded by anything a person does in the workspace.
Authorizations
A Custral secret API key (sk_…), created in Settings → Applications. Sent as Authorization: Bearer sk_…. The X-Api-Key: sk_… header is also accepted and takes precedence. Never expose a secret key in a browser.
Path Parameters
Query Parameters
Page size, 1-200. Defaults to 50 - this endpoint always pages.
1 <= x <= 200Rows to skip, for the next page.
x >= 0