Skip to content

Caching Responses

Caching API responses is a crucial strategy to optimize performance, reduce latency, and minimize the number of requests made to our API. This not only enhances user experience but also helps you stay within your rate limits.

  • Data storage is only permitted with an active contract or license
  • All stored data must be deleted immediately upon termination or expiration of this license or contract.
  • Cached data cannot be shared with unlicensed third parties

If you need to guarantee that user logs or historical protocols remain fully reproducible beyond the guaranteed compatibility period, store the final evaluation results and the minimum required protocol information on your side. However, this must be done in accordance with your Newtrition Data license. Storing or caching API responses, individual food entries, nutrient data, serving sizes, processing states, or other database-derived food data is only permitted while you maintain a valid and active license. Such cached or stored API data must be deleted when the license or contract ends and must not be shared with unlicensed third parties. To support long-term user history without violating these restrictions, avoid storing full reusable food objects. Instead, store final user-facing protocol or evaluation results where legally permitted and technically required.