Description
Delete ALL Access tokens for a specific user.
Note:
Calling this API requires the use of the LibrarySecret, so it must be invoked in the backend to ensure key security.
The UserId parameter must be specified; therefore, when creating an access token, if you plan to proactively delete the corresponding access token later, you also need to specify UserId during creation.
If ClientId is specified and it is not an empty string, only delete the access tokens with the specified ClientId under the designated UserId(s).
If SessionId is specified and it is not an empty string, only delete the access tokens with the specified SessionId under the designated UserId(s).
When both ClientId and SessionId are specified as non-empty strings, only the access tokens that have both the specified ClientId and SessionId under the designated UserId(s) are deleted.
Request
Request Example
DELETE /api/v1/token/{LibraryId}?library_secret={LibrarySecret}&user_id={UserIds}&client_id={ClientIds}&session_id={SessionIds}
Request Parameter
|
LibraryId | Media Library ID, obtain it after creating a media library in the media hosting console. See Create Media Library | String | Yes |
LibrarySecret | Media Library Key, obtain it after creating a media library in the media hosting console. See Create Media Library | String | Yes |
UserIds | User identity recognition, multiple UserIds separated by ,, with a maximum of 10 at once. If exceeding 10, call in batches. | String | Yes |
ClientIds | Client identification, multiple ClientIds separated by ,, with a maximum of 100 at once. If exceeding 100, call in batches. | String | No |
SessionIds | Session identification, multiple SessionIds separated by ,, with a maximum of 100 at once. If exceeding 100, call in batches. | String | No |
Request Body
Null.
Response
Response code
Deleted successfully, returns HTTP 204 No Content.
Response Body
Null. No response body.
Error Codes
This request operation has no special error messages. For common error messages, see Error Codes.