Sub Users
Revoke sub user
Changed onRevokes (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.
post/sub_user/remove/{sub_user_id}
Request
- Base URLhttps://api.treasuredata.com/v3
- AuthHTTP td1
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
sub_user_idId required(unresolved $ref)
Response
OK
Changes
- info
endpoint added
- info