curl -X DELETE 'https://rest-api.argosidentity.com/v3/submission/tokens' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: text/plain' \
  -d '{
  "tokenId": [
    "user001a",
    "api.key.01",
    "token-123-abc", 
    "session_data_01"
  ]
}'

{
  "success": true,
  "message": "Successfully deleted 3 tokens",
  "summary": {
    "totalSubmitted": 3,
    "deleted": 3,
    "notFound": 0,
    "failed": 0
  }
}
Securely delete registered tokens. You can delete up to 100 tokens in batch, with partial processing support.
Token deletion is an irreversible operation. Please review carefully before deletion.

​
Basic Information

​
method
string
required
DELETE
​
url
string
required
https://rest-api.argosidentity.com/v3/submission/tokens

​
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

​
Data Security

Deleted token data is completely removed and cannot be recovered. In private mode, the deletion process also proceeds with encryption.

​
Authentication

​
x-api-key
string
required
Set your project API key.
​
Content-Type
string
required
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.
x-api-key: {{YOUR_API_KEY}}
Content-Type: text/plain

​
Request Parameters

​
Request Body

​
tokenId
Array<String>
required
Array of token IDs to delete (maximum 100)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
curl -X DELETE 'https://rest-api.argosidentity.com/v3/submission/tokens' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: text/plain' \
  -d '{
  "tokenId": [
    "user001a",
    "api.key.01",
    "token-123-abc", 
    "session_data_01"
  ]
}'

​
Response

​
Success Response (200)

​
success
Boolean
Operation success status
​
message
String
Operation result message
​
summary
Object
Summary information
​
details
Object
Detailed information (included only when there are failures or non-existent tokens)
{
  "success": true,
  "message": "Successfully deleted 3 tokens",
  "summary": {
    "totalSubmitted": 3,
    "deleted": 3,
    "notFound": 0,
    "failed": 0
  }
}

​
Error Response (400/500)

​
errorCode
String
Error code
​
errorMessage
String
Error message
{
  "errorCode": "token_not_found",
  "errorMessage": "Token not found."
}

​
Token Policy

​
Limitations

Request limit: Maximum 100 token IDs per request Pool limit: Maximum 5,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 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

Error CodeHTTP StatusDescription
invalid_payload400Missing request payload or format error
invalid_path400Unsupported HTTP method
invalid_project400Missing project ID or invalid API key
internal_server_error500Internal server error
Error CodeHTTP StatusDescription
invalid_token_id400Missing token ID, empty value, or not an array
invalid_token_id_format400Token ID format rule violation
request_token_limit_exceeded400Request token count limit exceeded (100)
token_id_not_found400Requested token does not exist in pool

​
Usage Examples

1

Check tokens to delete

Verify if tokens exist before deletion.
curl -X GET 'https://rest-api.argosidentity.com/v3/submission/tokens?tokenId=user001a' \
  -H 'x-api-key: YOUR_API_KEY'
If the token exists, detailed information will be returned.
2

Execute token deletion

Delete the verified tokens.
curl -X DELETE 'https://rest-api.argosidentity.com/v3/submission/tokens' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: text/plain' \
  -d '{"tokenId": ["user001a", "api.key.01"]}'
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.