Skip to main content
If the rate limit for an endpoint is exceeded, you will receive a 429 error. To resolve this:
  • Wait for the rate limit window to reset
  • Check the specific rate limit value in the endpoint description
  • Consider implementing rate limiting in your code
CORS requests to this endpoint are forbidden for security reasons. Make the request from your backend instead of client-side.
These endpoints are restricted to B2B partner services only. To gain access:
  • Contact support@whitebit.com
  • Request permissions for Smartplan endpoints
  • Provide your use case details
There are two solutions:
  1. Open multiple WebSocket connections
  2. Use the equivalent HTTP method instead
For more details, see the Kline documentation.
The system only shows the last 100 deals by default. To see more:
  • Subscribe to our WebSocket feed
  • Accumulate and store the data on your side
  • Process the data as needed for your use case
To resolve nonce errors:
  1. Debug your code implementation
  2. Recreate your API keys
  3. Ensure your system time is properly synchronized
When making transfers and withdrawals:
  • Wait for transfers to complete (approximately 2 seconds)
  • Don’t initiate withdrawals before transfer completion
  • Implement proper error handling for transfer states
This occurs when the withdrawal amount plus the fee exceeds your available balance. Remember to:
  • Account for withdrawal fees in your calculations
  • Check the fees documentation
  • Ensure sufficient balance for both amount and fees
Yes, HTTPS is required:
  • Communication occurs over port 443
  • SSL/TLS encryption is mandatory
  • HTTP connections are not supported
You can check currency status through the assets endpoint:
To maintain API key security:
  • Never share your API keys
  • Store keys securely (use environment variables)
  • Restrict IP addresses when possible
  • Use the minimum required permissions
  • Rotate keys periodically
If you suspect key compromise:
  1. Immediately delete the compromised key
  2. Review account activity for unauthorized actions
  3. Create new API keys with fresh permissions
  4. Update your application with the new keys
  5. Contact support if unauthorized activity is detected
For optimal API performance:
  • Use WebSocket for real-time data
  • Batch requests when possible
  • Implement proper rate limiting
  • Cache frequently accessed data
  • Monitor network latency
To handle disconnections effectively:
  • Implement automatic reconnection logic
  • Use exponential backoff for retries
  • Maintain local order state
  • Log all critical operations
  • Set up monitoring and alerts