Skip to main content
Prefix: /v1/developer/observability. Requests are scoped to the key’s workspace. End-user labels are attribution; they cannot expand ownership.

​
Trace query

category must be model, tool, compute or all. from and to are UTC calendar dates formatted YYYY-MM-DD. The interval is limited to 93 calendar days inclusive. When requestId is supplied, category must be a specific category rather than all. Request IDs use 64 lowercase hexadecimal characters. Cursors are opaque, bounded values.
The key needs read access to the selected category. category all requires all three category read scopes. Follow returned pagination; one page is not a complete export.

​
Sessions and users

Page numbers are 1–9999. Use returned session/account identifiers for the execution filters. A caller-supplied endUserId is not the same as a verified platform account identity. See sessions and attribution. Sessions group captured executions; they do not automatically import customer history that was never sent through Dreamtune. Only retained content is replayable.

​
Captured content and media

The content response includes requestId, sessionId, data, media and nextCursor. Stage data includes id, stage, startTime, input and output, with prompt name and version when captured. Media entries include id, contentType, size, url and expiresAt. Use the content cursor until all required pages have been read. Signed media URLs expire. Refresh authorized content access instead of treating a URL as permanent public storage. Historical traces may lack capture or media that was not archived. See media.

​
Feedback and assessments

value is 0 or 1; comment is bounded to 500 characters. Feedback is one account/request assessment, not an editable chat message. Repeating it does not replace an existing assessment. Your application must provide a feedback button or another explicit collection flow. Langfuse does not know whether the user liked a response unless feedback is submitted or a configured evaluator assesses it. Scores are judgments with specific criteria; they are not proof of factual accuracy or agreement violation. Some requests may have no assessment yet. Prompt creation and selection are documented separately in prompt API.