---
title: "Clear user"
method: POST
path: "/action/clear-user"
---

# Clear user

`POST /action/clear-user`

Clears the user context for all subsequent events.

## Request body

- union
  - ClearUserWithSessionToken
    - `session_token` string, required — A token returned by the SDK for the device session established upon SDK initialization.
  - ClearUserWithSecureSessionToken
    - `secured_session_token` string, required — A cryptographically signed token returned by the SDK's `getSecureSessionToken()` method. Provides enhanced security through device binding and anti-replay protection.

## Response `201`

The user association has been cleared for the device.

- object
  - `success` boolean — Defines if the operation was successful.
  - `message` string — A human-readable confirmation message.

## Other responses

- `400` — Bad request
- `401` — Invalid authentication
- `403` — Invalid authorization
- `429` — Rate limit reached
- `463` — Blacklisted token—Returned when Fraud Prevention detects repeated or abusive token/payload misuse within a short time window (e.g., reuse of expired tokens, token caching/automation, or repeated invalid requests, including highly repetitive invalid request values). The response body contains the underlying error code (e.g., expired session token). Clients should identify and stop the source of invalid requests. Other authorization failures that do not trigger blacklisting return 403 Forbidden.
- `500` — Internal error

---

[API](https://skmtc.dev/transmitsecurity/apis/client-actions.md) · [All operations](https://skmtc.dev/transmitsecurity/apis/client-actions/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/transmitsecurity/client-actions/revisions/8adcc6e67945/schema)