/api/v1/access-grants/{id}/activityAccess log of a grant
The grant's log rows, newest first, by cursor. Grant events (grant_created, grant_changed, grant_revoked) name who acted: via is the API key (by its label) or the OAuth app, and is null for the dashboard; actorId is the user it acted for. read rows carry one count per passport, channel and day.
No IP addresses are kept, and rows are deleted after 24 months. An id that belongs to another company answers 404.
Who may call it. An API key only when its owner switched on "May manage access grants" for that key on the Developer page (off by default; otherwise 403 access_grants_not_enabled). An OAuth token needs the access_grants:read scope and an editor role or above.
Path parameters
- idrequired
string (24 hex chars)
Access grant ID.
Query parameters
- limit
integer
Page size, 1 to 100 (default 50).
- cursor
string (24 hex chars)
The
nextCursorof the previous page.
Headers
- Authorizationrequired
string
Bearer <token>— either atp_API key (Developer → API Keys; simplest, for server-to-server) or an OAuth 2.0 access token (Developer → OAuth Apps; for user-authorized apps, scoped + revocable). The Authentication page has the full OAuth flow and scope list.e.g. Bearer tp_REDACTED_xxxxxxxxxxxx
Request
curl -sS https://app.tracepass.eu/api/v1/access-grants/6650c1d2e3f4a5b6c7d8e9f0/activity \
-H "Authorization: Bearer tp_REDACTED_xxxxxxxxxxxx"Response
{
"data": [
{
"id": "6650d2e3f4a5b6c7d8e9f0a1",
"kind": "grant_created",
"day": "2026-06-01T00:00:00.000Z",
"channel": null,
"passportId": null,
"count": null,
"detail": null,
"actorId": "6650a0a0a0a0a0a0a0a0a0a0",
"via": { "kind": "api_key", "keyId": "6650b0b0b0b0b0b0b0b0b0b0", "label": "SAP prod" },
"lastAt": "2026-06-01T09:30:00.000Z"
}
],
"nextCursor": null
}