Skip to main content

​
Error Responses

The CoinStats API uses standard HTTP status codes to indicate the success or failure of requests.

​
HTTP Status Codes

All error responses share the following shape:
The requestId is a unique identifier for the request — include it when contacting support.

​
Common Error Responses

​
400 Bad Request

Invalid parameters:

​
401 Unauthorized

Invalid or missing API key:

​
403 Forbidden

API key does not have permission for this endpoint (e.g., plan-restricted endpoint):

​
404 Not Found

Resource not found:

​
409 Conflict

Transactions not synced:

​
429 Too Many Requests

Rate limit or credit limit exceeded:

​
503 Service Unavailable

Upstream service temporarily unavailable (credits charged for the request are automatically refunded):

​
Troubleshooting

​
Authentication Issues

  1. Check your API key: Ensure you’re using the correct API key
  2. Verify header format: Make sure the X-API-KEY header is properly set
  3. Check key permissions: Ensure your API key has the necessary permissions

​
Rate Limiting

  1. Monitor credit usage: Check your credit consumption in the dashboard
  2. Optimize requests: Use filters and pagination to reduce data transfer
  3. Upgrade plan: Consider upgrading if you consistently hit limits

​
Data Not Found

  1. Verify parameters: Check that all required parameters are provided
  2. Check data availability: Some data might not be available for all coins/time periods
  3. Use correct IDs: Ensure you’re using the correct coin IDs from the API

​
Wallet/Transaction Issues

  1. Sync transactions: Call the sync endpoint before requesting transaction data
  2. Check wallet address: Ensure the wallet address is valid and supported
  3. Verify blockchain: Make sure the blockchain is supported by CoinStats