Important: This API is Not a Database#
Our API is designed to serve data, not to act as a primary data storage solution for your application. Do not use this API as your database. Instead, implement proper caching mechanisms on your side to store and manage frequently accessed data locally.Mandatory Client-Side Caching#
All API consumers must implement client-side caching. This is not optional—it's a requirement for successful integration. Consider implementing:Response caching with appropriate TTL (Time To Live) values
Local data storage for frequently accessed information
Smart cache invalidation strategies to ensure data freshness
Fallback mechanisms when the API is temporarily unavailable
Strict Rate Limiting#
All API endpoints are protected by strictly enforced rate limits to ensure fair usage and system stability. Exceeding these limits will result in:HTTP 429 (Too Many Requests) status codes
Temporary blocking of your requests
Potential disruption to your application's functionality
Integration Best Practices#
To avoid rate limit issues and ensure reliable operation:1.
Cache aggressively - Store API responses locally and reuse them
2.
Implement exponential backoff when receiving 429 responses
3.
Monitor your request patterns to stay within limits
4.
Use conditional requests (ETags, If-Modified-Since) when available
5.
Batch requests where the API supports it
Consequences of Non-Compliance#
Applications that consistently exceed rate limits or attempt to use our API as a database replacement may experience:Extended blocking periods
Potential account suspension
Modified at 2025-07-28 13:35:15
