Overview
Verifies whether a token exists on Solana. This endpoint is useful for validating token addresses before attempting operations.URL Parameters
The Solana token mint address to verify
Response
Whether the token exists on-chain
The token address that was checked (echoed back)
Full asset information from Helius API (only present if token exists)
Error message if verification failed (optional)
Token Exists Response
Token Not Found Response
API Error Response
HTTP Status Codes
200 - OK
200 - OK
Request processed successfully. Check the
exists field to determine if token was found.400 - Bad Request
400 - Bad Request
500 - Server Error
500 - Server Error
Caching Behavior
This endpoint implements permanent caching for performance:Cache Strategy
Cache Strategy
- Exists = true: Cached permanently (tokens can’t be “un-created”)
- Exists = false: Cached permanently only for confirmed “RecordNotFound” errors
- API errors: Not cached, allowing retries for transient issues
- Cache key: Token address
Cache Performance
Cache Performance
- First request: Calls Helius API (~200-500ms)
- Subsequent requests: Instant response from memory cache
- Cache hits: Logged to server console for monitoring
- Memory usage: Minimal overhead per cached token
Error Handling
The endpoint handles various error scenarios:RecordNotFound (-32000)
RecordNotFound (-32000)
Helius Response: Token definitively doesn’t existThis result is cached permanently.
API Errors
API Errors
Helius Response: Network, rate limiting, or service issuesThis result is NOT cached, allowing retries.
Unexpected Format
Unexpected Format
Helius Response: Valid response but unexpected structureThis result is NOT cached.
Network Errors
Network Errors
Client/Network: Connection issues, timeoutsInternal errors are not exposed to prevent information disclosure.
Rate Limiting
This endpoint is subject to rate limiting:- 8 requests per IP per 2-minute window
- Returns HTTP 429 when limit exceeded
- Note: Cached responses don’t count against rate limits
Use Cases
Pre-validation
Pre-validation
Verify tokens before attempting operations:
Token Discovery
Token Discovery
Check if user-provided addresses are valid:
Claims Validation
Claims Validation
Verify tokens before checking claim eligibility:
Asset Information
When a token exists, the response includes rich metadata:Token Metadata
Token Metadata
- Name, symbol, description
- Image/logo URLs
- JSON metadata URI
- Creator information
Token Program Info
Token Program Info
- Total supply
- Decimal places
- Token program (Token Program vs Token-2022)
- Mint authority status
Additional Data
Additional Data
- Compression status
- NFT collection info (if applicable)
- Transfer restrictions
- Extensions (if Token-2022)
Related Endpoints
/health- Check if Helius API key is configured/claims/:tokenAddress- Check claims for verified tokens/launch- Launch new tokens (verify they don’t exist first)
