Error Handling & Response Codes
Common Error Scenarios
1. Wildcard Instrument Subscription Error
Error Response:"instrument": "ALL"
or similar wildcard patterns.
Solution:
2. Subscription Limit Exceeded
Error Response:3. Invalid API Key
Error: Connection closes with messageinvalid api key '<api_key>'
Solution: Verify API key and permissions:
Production Error Handling Patterns
Robust Reconnection Logic
Message Processing & Buffering
Advanced Configuration
Connection Optimization
Multiple Endpoint Strategy:Health Monitoring
Enterprise Features & Customization
Custom Rate Limits
Enterprise customers can request custom configurations:Advanced Subscription Patterns
Conditional Subscriptions:Troubleshooting Checklist
Connection Issues
- Verify API key is valid and active
- Check network connectivity and firewall settings
- Ensure proper WebSocket library configuration
- Verify endpoint URL is correct for data type
Subscription Issues
- Confirm subscription parameters are valid
- Check subscription limits haven’t been exceeded
- Verify exchange and pair names are correct
- Ensure proper JSON-RPC 2.0 format
Performance Issues
- Monitor message processing latency
- Check for memory leaks in message handling
- Verify connection distribution across endpoints
- Review subscription patterns for efficiency
Data Quality Issues
- Implement message deduplication
- Add timestamp validation
- Monitor for missing sequence numbers
- Verify data format expectations
Getting Support
For enterprise-level support and custom configurations:- Technical Issues: Contact support with connection logs and error messages
- Custom Rate Limits: Reach out to sales team with requirements
- Performance Optimization: Schedule consultation for high-volume use cases
- Integration Support: Request dedicated technical account management