The events endpoint gives you programmatic access to the raw event log for any project. You can filter by model, status, time range, environment, and user ID, making it useful for building custom dashboards, exporting data, or auditing specific LLM calls. Results are cursor-paginated — when there are more records beyond your current page, the response includes aDocumentation Index
Fetch the complete documentation index at: https://docs.lumiqtrace.com/llms.txt
Use this file to discover all available pages before exploring further.
nextCursor value you pass in the next request.
Endpoint
Authorization: Bearer <token> (see Authentication)
Query Parameters
The ID of the project whose events you want to retrieve.
Filter to events from a specific model. Example:
gpt-4o, claude-sonnet-4-6.Filter by event status. One of
success, error, timeout, rate_limited, or cancelled.ISO 8601 UTC timestamp. Only return events at or after this time. Example:
2026-04-01T00:00:00.000Z.ISO 8601 UTC timestamp. Only return events before or at this time.
Filter by deployment environment. Example:
production, staging.Filter to events attributed to a specific user ID in your application.
Pagination cursor from the previous response’s
nextCursor field. Omit to start from the beginning.Maximum number of events to return. Default
50, maximum 200.Example Request
Response
200 OKArray of event objects matching your filters. See the Ingest Events page for the full event schema.
Opaque cursor string to pass as the
cursor query parameter to retrieve the next page. null when you have reached the last page.Total number of events matching your filters across all pages.
Pagination Example
To page through all results, keep requesting untilnextCursor is null:
TypeScript