Error Responses
The CoinStats API uses standard HTTP status codes to indicate the success or failure of requests.HTTP Status Codes
Status Code | Description |
---|---|
200 | Success - Request completed successfully |
400 | Bad Request - Invalid parameters or request format |
401 | Unauthorized - Invalid or missing API key |
404 | Not Found - Resource not found |
409 | Conflict - Resource conflict (e.g., transactions not synced) |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error - Server error |
Common Error Responses
401 Unauthorized
Invalid or missing API key:400 Bad Request
Invalid parameters:404 Not Found
Resource not found:409 Conflict
Transactions not synced:429 Too Many Requests
Rate limit exceeded:Troubleshooting
Authentication Issues
- Check your API key: Ensure you’re using the correct API key
- Verify header format: Make sure the
X-API-KEY
header is properly set - Check key permissions: Ensure your API key has the necessary permissions
Rate Limiting
- Monitor credit usage: Check your credit consumption in the dashboard
- Optimize requests: Use filters and pagination to reduce data transfer
- Upgrade plan: Consider upgrading if you consistently hit limits
Data Not Found
- Verify parameters: Check that all required parameters are provided
- Check data availability: Some data might not be available for all coins/time periods
- Use correct IDs: Ensure you’re using the correct coin IDs from the API
Wallet/Transaction Issues
- Sync transactions: Call the sync endpoint before requesting transaction data
- Check wallet address: Ensure the wallet address is valid and supported
- Verify blockchain: Make sure the blockchain is supported by CoinStats