Skip to main content
Logs from every run are forwarded to Loki and exposed via two endpoints — one for everything you’ve ever run, one scoped to a specific execution. The platform tags log lines with your user_id and the run’s execution_id, so you only ever see logs you own.

​
Per-execution logs

GET /api/v2/external/logs/execution/{execution_id}
QueryDefaultRangePurpose
limit10001–10000Maximum log entries to return
hours241–168Look-back window in hours
This is the right endpoint to grep through a single run’s output after it finishes — particularly useful when stdout/stderr were too large to surface inline in the run record. 
curl "https://api.lyceum.technology/api/v2/external/logs/execution/$EXEC?limit=5000&hours=2" \
  -H "Authorization: Bearer $LYCEUM_API_KEY"

​
Cross-run logs

GET /api/v2/external/logs/user
QueryDefaultRangePurpose
limit1001–5000Maximum log entries to return
hours11–24Look-back window in hours
Returns log lines from every run on your account in the window. Useful for spot-checking recent activity or building a basic activity feed for a custom dashboard.

​
What’s logged

Anything your code writes to stdout or stderr is captured. Lyceum doesn’t inject its own log lines into your output; what you print is what you get back, plus any platform-level events surfaced as separate log streams.