Skip to main content
AccessOwl emits webhook events throughout the access revocation lifecycle. All revocation event payloads share a common data structure:
FieldTypeDescription
idstringThe UUID of the revocation
affected_userobjectThe user whose access is being revoked
requested_byobjectThe user who initiated the revocation
applicationobjectThe application the access is being revoked from
objectobjectThe specific resource within the application
revocation_reasonstringThe reason provided for the revocation
created_atstringISO 8601 timestamp of when the revocation was created
Fired when an access revocation is initiated.
{
  "affected_user": {
    "email": "john.doe@example.com",
    "full_name": "John Doe",
    "id": "8b15e986-84ac-4dbc-8e66-c82ebf3d2fc2"
  },
  "application": {
    "id": "c4d5e6f7-a8b9-0123-cdef-456789abcdef",
    "title": "GitHub"
  },
  "created_at": "2022-07-13T23:42:00Z",
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "object": {
    "id": "d5e6f7a8-b9c0-1234-defa-56789abcdef0",
    "title": "Engineering Team"
  },
  "requested_by": {
    "email": "admin@example.com",
    "full_name": "Admin User",
    "id": "5a3e57df-2d08-46be-b5bd-b3ea505a3d26"
  },
  "revocation_reason": "Employee offboarded"
}