Skip to content
Evershell Docs

PromQL-shaped aggregation over a single workspace's audit log

GET
/workspaces/{id}/audit/stats
 
curl --request GET \
  --url 'https://your-org.evershell.ai/v1/workspaces/example/audit/stats?time_bucket=auto&metric=count' \
  --header 'Authorization: Bearer <token>'

GET /audit/stats pinned to one workspace — the same per-scope visibility as GET /workspaces/{id}/audit, then a workspace_id filter.

Permissions: any of audit:read, audit:read:own, workspace:read, workspace:read:own — the grants union the same way as GET /workspaces/{id}/audit. Equivalent to GET /audit/stats?filter=workspace_id=<id>; this route adds the workspace_id filter for the caller and returns 404 for a workspace in another org.

Same query model as GET /audit/stats: group_by, time_bucket, bucket_by, metric, top, filter, from, to all behave identically.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string

Query Parameters

Section titled “Query Parameters ”
group_by
string
time_bucket
string
Allowed values: auto 5m 15m 1h 6h 1d
bucket_by
string
metric
string
default: count
top
string
filter
Array<string>
from
string format: date-time
to
string format: date-time

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json
object
buckets
required
Array<object>
object
group
required
object
key
additional properties
string
bucket
string
value
required
number
Example generated
{
  "buckets": [
    {
      "group": {
        "additionalProperty": "example"
      },
      "bucket": "example",
      "value": 1
    }
  ]
}

400

Section titled “400 ”

Invalid query (unknown dimension / bad metric grammar).

Media type application/json
object
error
required
object
code
required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string
message
required

Human-readable summary

string
request_id
required

Server-generated request id for correlating logs

string
details

Optional structured context. Validation errors land at details.fields as a per-field map.

object
key
additional properties
any
Example 
{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}

404

Section titled “404 ”

Resource not found in the caller’s org

Media type application/json
object
error
required
object
code
required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string
message
required

Human-readable summary

string
request_id
required

Server-generated request id for correlating logs

string
details

Optional structured context. Validation errors land at details.fields as a per-field map.

object
key
additional properties
any
Example 
{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}