You can transmit data securely through private mode and encryption security features.
Basic Information
string
required
POST
string
required
Security Settings
Encryption Option
- 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
Authentication
string
required
Set your project API key.
string
required
Set the MIME type of the request body.
Request Parameters
Request Body
Array<String>
required
Array of token IDs to add (maximum 500 per request)Token ID format constraints:
- 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
Operation success status
String
Operation result message
Object
Summary information
Object
Detailed information (included only when failures occur)
Error Response (400/500)
String
required
Error code
String
required
Error message
Object
Error details (optional)
Token Policy
Limitations
Partial Handling
POST requests are processed partially for token IDs.
Token IDs that already exist in the pool will be overwritten, and no separate duplication error is returned.
- Token IDs existing in pool:
tokenA,tokenB,tokenC - POST request:
tokenA,tokenC,tokenD - Pool after request completion:
tokenA,tokenB,tokenC,tokenD
Error Codes
Common Errors
Token Related Errors
Content-Type Notice: For POST requests, when using
Content-Type: application/json causes an error, set the header to text/plain instead.