This guide covers advanced error handling, troubleshooting scenarios, and production-ready configuration for Amberdata’s WebSocket services.
Error Handling & Response Codes
This section describes common WebSocket subscription errors and how to resolve them.
Common Error Scenarios
1. Wildcards Not Supported for This Feature
Wildcard subscriptions are not supported for Tickers or Order Book Event streams.
Error Response:
Cause: Attempting to subscribe to Tickers or Order Book Events without explicitly specifying both:
Solution:
2. Invalid Subscription Error
Error Response:
Cause: Attempting to subscribe with non-existent or misspelled subscription name.
Solution:
3. Invalid API Key
Error: Connection closes with message invalid api key '<api_key>'
Solution: Verify API key and permissions:
4. Missing API Key
Error Response:
Cause: Attempting to connect/subscribe with a missing API key.
Solution:
5. Missing Parameter(s)
Error Response:
Cause: Attempting to subscribe with no parameters.
Solution:
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
Subscription Issues
Data Quality Issues
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
Enterprise customers receive priority support with guaranteed response times and dedicated infrastructure options.