# Revoke sub user

Revokes (soft-destroys) a sub user and every credential it holds: its API keys are deleted, and its OAuth access tokens, refresh tokens and unexchanged authorization codes are revoked.
It does not work the other way round: deleting one of a sub user's API keys leaves the sub user and its other credentials alone. Revoking one of its OAuth tokens does deactivate it, because a sub user exists for one authorization -- see `POST /oauth_token/remove/{oauth_token_id}`.
An administrator may revoke any sub user in the account; a non-administrator only their own. Sub users themselves are refused entirely.

Endpoint: POST /sub_user/remove/{sub_user_id}
Version: 3
Security: ApiKeyAuth

## Security:

  - `ApiKeyAuth` (unknown)
    http TD1

## Path parameters:

  - `sub_user_id` (integer, required)

## Response 200:

  - `200` (unknown)
    OK

## Response 200 fields (application/json):

  - `sub_user` (object, required)

  - `sub_user.id` (integer, required)
    unique identifier of the sub user
    Example: 123

  - `sub_user.email` (string, required)
    the synthetic, non-deliverable email of the sub user