Introduction
This section covers best practices for securing your Whalemate API integration and how to get support in case of problems.
🔒 Security and Best Practices​
To ensure the security of your application, follow these best practices:
1API Key Protection
- Do not share your API Key in public repositories, forums or with unauthorized third parties.
- Use environment variables to store your API Key in production.
- If you think your key has been compromised, revoke it immediately and generate a new one.
2Key Rotation
- Implement a key rotation strategy from time to time to minimize risks.
- Use different API Keys for development and production environments.
3Use of HTTPS
- All requests must be made via HTTPS to avoid man-in-the-middle attacks.
- Block HTTP traffic on your server to prevent insecure connections.
4Rate Limiting
- To prevent abuse and improve stability, Whalemate imposes limits on the number of requests per minute.
- If you exceed the limits, you will receive a
429 Too Many Requestsresponse.
Solution: Implement retries with exponential backoff.
💬 Support and Contact.​
If you're having trouble, here are some options for getting help:
Check the Documentation​
Before contacting us, please review the full documentation for solutions to common problems.
Technical Support​
If you need direct help, contact us at support@whalemate.com.
Our goal is to make your experience seamless and successful. If you encounter any issues or need clarification, don't hesitate to get in touch with us.
Thank you for using Whalemate! 🚀