Basic Information
DELETE
Security Settings
Encrypted Transmission
When the Secure Data Transmission option is enabled, requests and responses are encrypted with AES-256.
- Encryption method: AES-256
- Coverage: Request and response data
- Compatibility: Same encryption/decryption method as POST/submission, PATCH/submission, GET/submission
- Secure Data Transfer Options
Data Security
Deleted token data is completely removed and cannot be recovered. In secure data transmission, the deletion process also proceeds with encryption.
Authentication
Set your project API key.
Set the MIME type of the request body.
Token Deletion Types
- tokenId specified deletion
- Delete specific tokenId (maximum 500 per request)
- Time-based N deletion
- Delete N tokens based on submission order and count (maximum 5,000 per request)
Request Parameters
Request Body
- tokenId specified deletion
- Time-based N token deletion
Array of token IDs to delete (maximum 500)Token ID format:
- Length: 8 Byte ~ 64 Byte
- Allowed characters: Letters (a-z, A-Z), numbers (0-9), hyphens (-), underscores (_), periods (.)
- Restrictions: No spaces, tabs, or newline characters
- Start/End: Must start and end with letters or numbers only
Response
Success Response (200)
- tokenId specified deletion
- Time-based N token deletion
Error Response (400/500)
Error code
Error message
Token Policy
Limitations
Partial Handling
DELETE requests are processed partially for token IDs.
Token IDs that do not exist in the pool are indicated in the ‘notFound’ field of the response, and only existing token IDs are deleted.
- Token IDs existing in pool:
tokenA,tokenB,tokenC - DELETE request:
tokenA,tokenC,tokenD - Pool after request completion:
tokenB - Response details.notFound: [
tokenD]
Security Considerations
Complete Data Deletion
Tokens deleted in private mode are completely removed in an encrypted state and cannot be recovered.
- Secure deletion: Complete removal from database
- Encryption processing: AES-256/GCM-256 encryption applied to deletion process as well
- Audit logs: Deletion operation records maintained (excluding token contents)
Access Control
Error Codes
Common Errors
| Error Code | HTTP Status | Description |
|---|---|---|
| invalid_payload | 400 | Missing request payload or format error |
| invalid_path | 400 | Unsupported HTTP method |
| invalid_project | 400 | Missing project ID or invalid API key |
| invalid_query_parameters | 400 | Missing query parameters or format error |
| invalid_order | 400 | Query parameter order format error |
| internal_server_error | 500 | Internal server error |
Token Related Errors
| Error Code | HTTP Status | Description |
|---|---|---|
| invalid_token_id | 400 | Missing token ID, empty value, or not an array |
| invalid_token_id_format | 400 | Token ID format rule violation |
| invalid_token_id_type | 400 | Token ID is not a string |
| invalid_token_id_length | 400 | Token ID length outside 8-64 character range |
| invalid_token_id_whitespace | 400 | Token ID contains whitespace characters |
| invalid_token_id_characters | 400 | Token ID contains disallowed characters |
| invalid_token_id_start | 400 | Token ID does not start with letter/number |
| invalid_token_id_end | 400 | Token ID does not end with letter/number |
| request_token_limit_exceeded | 400 | Request token count limit exceeded (500) |
| token_limit_exceeded | 400 | Project token total count limit exceeded (100,000) |
| token_id_not_found | 400 | Requested token does not exist in pool |
| token_id_details_not_found | 400 | Token details retrieval failed |
| delete_token_limit_exceeded | 400 | Time-based bulk deletion request count exceeded (5000) |
Usage Examples
1
Check tokens to delete
Verify if tokens exist before deletion.
If the token exists, detailed information will be returned.
2
Execute token deletion
Delete the verified tokens.
Types: token specified deletion, time-based token deletion
3
Check deletion results
Verify the deletion results in the response.
You can check the number of successfully deleted tokens in the
summary.deleted field.Content-Type Notice: For DELETE requests, when using
Content-Type: application/json causes an error, set the header to text/plain instead.