Query runtime log data
A query can use only the public alias runtime_logs_v1. CTEs, subqueries, UNION, and EXCEPT are permitted.
The root key must have the project.*.read_runtime_logs permission.
Unkey limits each query to the workspace of the root key. To get the logs of one project, app, environment, or deployment, add a filter on project_id, app_id, environment_id, or deployment_id.
The workspace retention period and the workspace query limits apply.
For the table, the columns, and more query examples, see Query runtime logs.
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
The SQL query for your runtime log data.
A query can use only the public alias runtime_logs_v1. The physical default.* table name is not permitted. CTEs, subqueries, UNION, and EXCEPT are permitted.
Only SELECT queries are permitted.
Unkey limits each query to the workspace of the root key. To get the logs of one project, app, environment, or deployment, add a filter on project_id, app_id, environment_id, or deployment_id.
The workspace retention period and the workspace query limits apply.
"SELECT time, severity, message FROM runtime_logs_v1 WHERE lower(message) LIKE '%timeout%' ORDER BY time DESC LIMIT 100"
Response
Query executed successfully
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
The runtime log rows that the query returned. The SELECT clause of the query sets the fields of each row.