Skip to main content
DELETE
Delete user (internal/domain)
Deletes a Syteca user. For domain users, this removes only the Syteca link — the AD account itself is unaffected. For Internal users, this permanently removes the user from Syteca.
For ACB deployments updated from a version prior to 1.2, switch to the https://{hostname}/EkranACB server in the Playground.

Permissions required

The Access Token must be issued to a user with the administrative User Management permission.

Common use cases

  • Offboarding automation — HRIS termination triggers user deletion in Syteca.
  • Contractor cleanup — Auto-delete contractor accounts after engagement end-date.
  • IdP deprovisioning — Okta / Azure AD removes the user → webhook calls this endpoint.

Historical session data is preserved

Deleting a user does not delete their historical session recordings or audit log entries. Their user name remains visible in session metadata for compliance retention; only the user account itself (permissions, group memberships, login capability) is removed.

Errors

See Status codes. Common errors:
  • 403 Forbidden — user lacks administrative User Management permission, or the request would delete the last user with User Management permission (preventing lockout).
  • 404 Not Found — user doesn’t exist.
Syteca prevents deletion of the last user with administrative User Management permission — this would lock all administrative access to the system. To replace the last User Management admin, create the replacement user with User Management permission first, then delete the prior user.

Get user details

Verify the user before deletion.

Remove from user group

Remove group membership without deleting the user.

Create internal user

Re-create if accidentally deleted.

API reference

Status codes.

Authorizations

Authorization
string
header
required

Access token for authentication

Path Parameters

userId
integer<int32>
required

ID of the user to delete (internal or domain)

Response

User was successfully deleted