List Kimchi Events

Lists Kimchi events of one type in the order they were recorded, using an
opaque cursor. Pages are bounded by one hour of recording time, so a page
can hold fewer items than pageSize, or none, while hasMore is true.
Clients keep calling with nextPageCursor until hasMore is false, and store
nextPageCursor to resume later. A record can be returned again with the
same id and a newer recorded_at when it is corrected or delivered again;
clients replace records by id. Records become available about two minutes
after they are recorded. An enterprise parent organization reading a
child organization must send the X-CastAi-Organization-Id header with the
child organization ID.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The ID of the organization.

Query Params
string

Required. The event type to export: "llm_usage" or "workspace_event".
The value also names the block that holds the type-specific fields of
each record.

string

The nextPageCursor of the previous page. Empty to start at startTime, or
at the organization's first record of the last 90 days when startTime is
not set.

int32

Maximum number of items to return. Defaults to 1000, which is also the
maximum; larger values are lowered to 1000. Must not be negative.

date-time

Where to start when cursor is empty: the export returns the records with
a recorded_at at or after this time. A time more than 90 days ago starts
90 days ago. A time in the future or within the last two minutes returns
an empty last page whose nextPageCursor starts at this time; calls with
that cursor return empty pages until records from this time are
available. Ignored when cursor is set, so the same request can be sent
again with each nextPageCursor.

Responses

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