Skip to main content
Securely delete registered tokens. You can delete up to 5,000 tokens in batch, with partial processing support.
Token deletion is an irreversible operation. Please review carefully before deletion.

Basic Information

string
required
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

string
required
Set your project API key.
string
Set the MIME type of the request body.
When using Content-Type: application/json for DELETE requests, if an error occurs, use text/plain instead.

Token Deletion Types

  1. tokenId specified deletion
  • Delete specific tokenId (maximum 500 per request)
  1. Time-based N deletion
  • Delete N tokens based on submission order and count (maximum 5,000 per request)

Request Parameters

Request Body

Array<String>
required
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)

Boolean
required
Operation success status
String
required
Operation result message
Object
required
Summary information
Object
Detailed information (included only when there are failures or non-existent tokens)

Error Response (400/500)

String
required
Error code
String
required
Error message

Token Policy

Limitations

Request limit: Maximum 5,000 token IDs per request Pool limit: Maximum 100,000 tokens managed per PID

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.
Example:
  • 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

Deletion permissions are controlled through API keys. Special care is required in API key management.

Error Codes

Common Errors

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
Deletion is executed immediately and cannot be undone.
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.
During bulk deletion, even if non-existent tokens are included, only existing tokens are selectively deleted. You can check the list of non-existent tokens in details.notFound.
Content-Type Notice: For DELETE requests, when using Content-Type: application/json causes an error, set the header to text/plain instead.