Skip to main content
Securely retrieve registered tokens. You can perform detailed retrieval of a single token or retrieval of the entire token list.
When the Secure Data Transmission option is enabled, response data is transmitted encrypted with AES-256.

Basic Information

string
required
GET

Security Settings

Encrypted Transmission

When Secure Data Transmission is enabled, all response data is protected with AES-256 encryption.
  • Encryption method: AES-256
  • Coverage: Response data
  • Compatibility: Same encryption/decryption method as POST/submission, PATCH/submission, DELETE/submission, Webhook
  • Secure Data Transfer Options

Authentication

string
required
Set your project API key.

Token Retrieval Types

  1. Single retrieval
  • Detailed retrieval of specific tokenId (1 per request)
  1. List retrieval
  • Entire token list retrieval: 10,000 per request
  • When registered tokenId exceeds 10,000, pagination fields (‘nextPageKeyId’, ‘nextPageKeyTime’) are provided
  1. Total count retrieval
  • Retrieve total count of registered tokens (entire N count per request)

Request Parameters

Query Parameters

String
Specific token ID
  • When provided: Single token detailed retrieval
  • When not provided: Entire token list retrieval
String
count
  • When provided: Retrieve only the total count of registered tokens
  • When not provided: Provide registered tokens and expiration status and count

Response

Success Response (200)

Boolean
required
Retrieval success status
String
required
Retrieved token ID
Object
required
Token data
You can use the data[‘expired’] value to check which tokens have expired among previously submitted ones and utilize it for DELETE-token operations.

Error Response (400/500)

String
required
Error code
String
required
Error message

Security Considerations

Data Protection

Token retrieval may contain sensitive information. Consider enabling the encryption option for security in production environments.
  • Encrypted transmission: Response data encryption through AES-256
  • Access control: Project-level access restriction through API keys
  • Pre-validation: API retrieval possible regardless of option activation status

Token Policy

Token Pool: Manage up to 100,000 tokens per PID Retrieval scope: Can only retrieve tokens within project scope

Error Codes

Common Errors

Usage Examples

1

Check entire token list

First, retrieve all tokens registered in the project.
You can check the total token count through the count field in the response.
2

Retrieve specific token details

Retrieve detailed information for a specific token.
You can check the token’s last update time through updateTime.
In encrypted environments, response data is also provided encrypted.
Decryption processing is required for this data.
For encryption and decryption methods, refer to Data Encryption and Decryption.