/api/v1/access-grants/{id}Revoke an access grant
Revoke a grant: its token stops working at once. Idempotent: revoking a grant that is already revoked answers 200 with it again. Only an id that is not your company's answers 404. An authority grant (an authority role or the authority tier) can only be revoked in the dashboard: through the API it answers 400 role_dashboard_only.
Revocation is not blocked by a past-due subscription, so a company can always cut access off. It counts as one v1 write when it revokes. The revocation is written to the grant's access log with the API key or app that made it. Honours Idempotency-Key.
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:write scope and a user who is an admin or owner.
Path parameters
- idrequired
string (24 hex chars)
Access grant ID.
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
- Idempotency-Key
string
UUID v4.
Request
curl -sS -X DELETE https://app.tracepass.eu/api/v1/access-grants/6650c1d2e3f4a5b6c7d8e9f0 \
-H "Authorization: Bearer tp_REDACTED_xxxxxxxxxxxx"Response
{
"data": {
"id": "6650c1d2e3f4a5b6c7d8e9f0",
"accessLevel": "restricted",
"label": "Buyer GmbH, order 4711",
"role": "purchaser",
"scope": { "kind": "passports", "ids": ["6650a1b2c3d4e5f6a7b8c9d0"] },
"purpose": null,
"evidence": null,
"state": "revoked",
"expiresAt": null,
"useCount": 0,
"createdAt": "2026-06-01T09:30:00.000Z"
}
}