specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Foodspark providerId: foodspark created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-06-02' reconciled: true tags: - Data - Food - Groceries - Restaurants - Web Scraping - Rate Limiting description: >- Foodspark does not publish a self-serve API with documented request rate limits, quotas, or rate-limit response headers. It operates as a managed data-as-a-service / web-scraping provider where data is delivered to customers via files or feeds after a sales engagement. The effective "rate" is the agreed scraping / refresh cadence negotiated per project, not a per-API-key throttle. No public 429/Retry-After semantics or X-RateLimit headers are documented. The single limit entry below reflects this negotiated cadence rather than an enforced technical throttle. sources: - https://www.foodspark.io/food-data-api/ - https://www.foodspark.io/pricing/ responseCodes: {} limits: - name: Negotiated Scraping / Refresh Cadence scope: contract metric: varies limit: see negotiated engagement; no published per-key rate limit applies: - Foodspark Food Data Service policies: - name: Negotiated Cadence description: >- Data freshness and extraction frequency are set per engagement (real-time, scheduled, or on-demand batch) rather than enforced as a public per-key request rate limit. - name: No Self-Serve Throttling description: >- Because there is no public self-serve API, there are no documented X-RateLimit headers, 429 throttling responses, or burst ceilings. Delivery volume and pace are governed by the service contract. maintainers: - FN: Kin Lane email: kin@apievangelist.com