name: Opendatasoft Explore API Rate Limits description: Rate limits for the Opendatasoft Explore API vary by portal deployment and user authentication status. Limits are communicated through standard HTTP response headers. The public.opendatasoft.com portal allows up to 10 million anonymous calls per day. Record retrieval is capped at 100 per request (up to 10,000 with offset pagination). url: https://help.opendatasoft.com/apis/ods-explore-v2/ headers: - name: X-RateLimit-Limit description: The total daily API call quota for the current user/IP on this portal - name: X-RateLimit-Remaining description: The number of API calls remaining in the current quota period - name: X-RateLimit-Reset description: Unix epoch timestamp indicating when the quota resets (daily reset) errors: - code: 429 message: Too Many Requests description: Returned when the daily call quota is exceeded. Clients should implement exponential backoff before retrying. limits: - scope: anonymous unit: day limit: 10000000 portal: public.opendatasoft.com note: Up to 10 million calls per day for unauthenticated users on the public portal. Other portals may have lower limits. - scope: authenticated unit: day limit: null note: Extended quotas for authenticated users, configured per portal by administrators. Check your profile page on the specific portal for your personal quota. - scope: records-per-request unit: request limit: 100 note: Default maximum records returned per API request - scope: records-with-offset unit: request limit: 10000 note: Maximum records accessible via offset pagination recommendations: - Implement exponential backoff when receiving 429 responses - Check X-RateLimit-Remaining in response headers to monitor quota usage - Use authenticated requests for higher quotas on portals where registration is available - Use the download/export endpoints for bulk data access instead of paginating through the records endpoint - Cache responses locally to minimize repeated identical API calls