Authentication
The Token Launch API is currently open access with no API keys required:- ✅ No authentication needed
- ✅ No API keys to manage
- ✅ IP-based rate limiting only
Need higher rate limits? DM @zcombinatorio on Twitter to discuss increased limits for your use case.
Rate Limiting
All endpoints use IP-based rate limiting:Current Limits
Standard Rate Limit
Standard Rate Limit
8 requests per IP per 2-minute window
- Applies to all endpoints uniformly
- Resets every 2 minutes
- No exceptions for different endpoint types
- Based on client IP address only
Rate Limit Exceeded
Rate Limit Exceeded
HTTP 429 - Too Many RequestsWhen this happens:
- Wait for the 2-minute window to reset
- Implement exponential backoff
- Consider caching responses when possible
Higher Limits Available
Higher Limits Available
Need more requests?For applications requiring higher rate limits:
- DM @zcombinatorio on Twitter
- Describe your use case and expected volume
- Custom rate limits can be arranged
- No cost for legitimate use cases
- Project description
- Expected requests per minute
- Use case (web app, bot, integration, etc.)
- Timeline for deployment
HTTP Status Codes
Success Codes
200 - OK
200 - OK
Successful RequestThe request was processed successfully. Response contains the requested data.Endpoints: All endpoints return 200 on success
Response: JSON object with requested data
Client Error Codes (4xx)
400 - Bad Request
400 - Bad Request
Invalid RequestThe request was malformed or contained invalid parameters.Common causes:
- Missing required fields
- Invalid parameter values
- Business logic violations
- Invalid Base58 addresses
404 - Not Found
404 - Not Found
Resource Not FoundThe requested resource doesn’t exist.Common causes:
- Token not found in database
- Invalid transaction keys
- Token not launched through this API
429 - Too Many Requests
429 - Too Many Requests
Rate LimitedClient has exceeded the IP-based rate limit.Rate limit: 8 requests per IP per 2-minute windowResponse:Solutions:
- Wait for rate limit window to reset (2 minutes)
- Implement exponential backoff
- Cache responses when possible
- DM @zcombinatorio for higher limits
Server Error Codes (5xx)
500 - Internal Server Error
500 - Internal Server Error
Server ErrorAn unexpected error occurred on the server.Common causes:Solutions:
- Configuration issues
- Blockchain network problems
- External service failures
- Database connectivity issues
- Retry the request (may be transient)
- Check
/health
endpoint - Report persistent issues to @zcombinatorio
Rate Limit Best Practices
Client-Side Implementation
Caching Strategies
Eligible for Caching
Eligible for Caching
Safe to cache:
- Token verification results (
/verify-token
) - Token launch confirmations (once completed)
- Health check results (short-term)
- Token existence: Permanent (tokens don’t get deleted)
- Health status: 30-60 seconds
- Launch confirmations: Permanent
Not Safe to Cache
Not Safe to Cache
Do not cache:
- Claim eligibility (
/claims/:tokenAddress
) - changes over time - Unsigned transactions (
/launch
,/claims/mint
) - time-sensitive - Error responses - may be transient
- Claim eligibility changes every 24 hours
- Transactions have expiration times
- Cached errors prevent retry of transient issues
Monitoring Rate Limits
Client-Side Tracking
Server Response Patterns
Look for these patterns in responses:Contact for Support
Need Help?
- Rate limit increases: DM @zcombinatorio
- Technical issues: Report persistent 500 errors
- Integration questions: Ask about best practices
- Feature requests: Suggest improvements