Retrieve management events with the Activity Log API

Retrieve management activity events for Sanity users, projects, and organizations.

The Activity Log API operates on the same versioning and authentication system as as other APIs.

Base URL: https://api.sanity.io

The Activity Log API requires API version 2021-02-01.

The Activity Log API requires an Access Manager robot token. User session cookies (sanitySession) will not work with this endpoint.

Your token only returns activity for organizations and projects that the robot token can access. If you do not pass organizationId or projectId, the API returns activity across your allowed organizations and projects.

Set your token before running the examples:

export SANITY_AUTH_TOKEN="<your-token>"

All requests use bearer token authentication:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?limit=10"

Use the JSON endpoint for app integrations:

GET /v2021-02-01/activity

Use the CSV endpoint for exports:

GET /v2021-02-01/activity/export/csv

The CSV endpoint uses the same filters as the JSON endpoint.

Use actorId for events performed by a user:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?actorId=<sanity-user-id>&limit=25"

Use userId for events where the user is the target of the activity:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?userId=<sanity-user-id>&limit=25"

You can combine these with projectId to get activity for a person within a
project:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?actorId=<sanity-user-id>&projectId=<project-id>&limit=25"

Use organizationId for organization-level activity:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?organizationId=<organization-id>&limit=25"

An organizationId query returns organization-level events. To retrieve project activity inside an organization, query the relevant projects with projectId. If you are using a user token and want all activity the user can see, omit both organizationId and projectId.

Do not combine organizationId and projectId to mean "organization activity plus project activity." Different filter names are combined, so the result must match both filters.

Use projectId for project activity:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id>&limit=25"

You can pass the same filter more than once to match any of the values:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id-a>&projectId=<project-id-b>&limit=25"

The JSON endpoint defaults to limit=10. Values above 100 are capped at
100.

Use offset to skip matching events:

# First page
curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id>&limit=25&offset=0"

# Second page
curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id>&limit=25&offset=25"

Offset pagination can shift if new events are created while you page through
results. For more stable exports or audits, use startTime and endTime to
work through fixed time windows.

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id>&startTime=2026-06-01T00:00:00Z&endTime=2026-06-09T23:59:59Z&limit=100"

CSV exports use the same filters as JSON responses.

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  -o activity-log.csv \
  "https://api.sanity.io/v2021-02-01/activity/export/csv?projectId=<project-id>&limit=5000"

CSV limits are different from JSON limits:

• If limit is omitted, CSV exports default to 10000 events.
• Values above 50000 are capped at 50000.
• Explicit values less than or equal to 10 use the CSV default of 10000.
• For a small CSV test request, use limit=11 or higher.

CSV headers are sorted alphabetically. Metadata keys appear as dynamic
metadata.<key> columns when present in the returned events.

Use the documented filters below to scope activity log results by user,
project, organization, activity type, and time range.

Repeated values for the same filter are matched as "any of these values." For
example, this returns events with either activity type:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?action=project.name.edit&action=organization.name.edit&limit=25"

Different filter names are combined. For example, this returns project activity
with the matching action during the specified time window:

curl -sS \
  -H "Authorization: Bearer $SANITY_AUTH_TOKEN" \
  "https://api.sanity.io/v2021-02-01/activity?projectId=<project-id>&action=project.name.edit&startTime=2026-06-01T00:00:00Z&endTime=2026-06-09T23:59:59Z&limit=25"

Error responses use this shape:

{
  "code": 400,
  "status": "Bad Request",
  "message": "duplicate parameter: limit"
}

Common errors:

These documented filters cannot be repeated:

limit
offset
startTime
endTime

For example, limit=10&limit=20 returns 400.

For a full list of available options for the endpoints mentioned in this article, see the Activity Log API reference documentation.