1. Agreement
These API Terms of Service ("Terms") govern your use of DietlyAPI, the developer API available at api.getdietly.com ("the API"), operated by Jelte Ludeke, based in the Netherlands ("we", "us"). By creating an account, requesting an API key, or sending requests to the API you agree to these Terms. If you do not agree, do not use the API.
These Terms cover the API product only. Use of the Dietly mobile app is governed by the separate app Terms of Service.
2. The service
DietlyAPI provides programmatic access to a nutrition database of over 4 million foods, including text search, barcode lookup, and food detail endpoints. Plans and their limits are described on the pricing page: Starter (free), Pro, Scale, and Enterprise (custom).
3. Accounts and API keys
- You can create an account with a username and password or by signing in with Google. Keep your credentials and API key confidential; you are responsible for all requests made with your key.
- If you believe your key has been compromised, rotate it from your dashboard immediately.
- One account per person or organization unless we agree otherwise. Sharing, sublicensing, or reselling API keys is not allowed.
- We may suspend or revoke keys that violate these Terms, abuse the service, or present a security risk.
4. Plans, billing, and payment
- Paid subscriptions (Pro, Scale) are sold by Dietly and processed by our payment provider Stripe on a secure checkout page; your card details never reach us. Your final total is shown before you confirm payment. Stripe handles your payment data under its own privacy policy.
- Subscriptions are billed monthly in euros and renew automatically until cancelled.
- Where offered, the Scale plan includes a 14-day free trial. You can cancel during the trial at no charge; after the trial the subscription converts to a regular paid subscription.
- You can cancel anytime from the billing portal linked in your dashboard. After cancelling you keep paid access until the end of the current billing period, after which your account returns to the free Starter plan. Your key and data are not deleted.
- Upgrades take effect immediately. Price changes apply only to subsequent renewal periods and we will give at least 30 days notice by email or on the site.
5. Refund policy
- First purchase: if the API does not work as described, contact us within 14 days of your first charge and we will approve a full refund request.
- Renewals: renewal charges can be refunded if you contact us within 14 days of the charge and the plan's paid capacity was not meaningfully used in that period. In other cases we may offer a prorated refund at our discretion.
- EU consumers: by starting a subscription you request immediate access to the service. This does not limit your statutory rights; the 14-day policy above is intended to meet or exceed the EU right of withdrawal for digital services.
- Refunds are issued by us through Stripe to your original payment method and remain subject to applicable statutory rights. To request one, use API support with your account username or invoice number. Never send your full API key. See also our standalone refund policy.
6. Rate limits and fair use
- Each plan has documented request limits (per minute, per IP or per account), listed on the pricing page. Requests over the limit receive HTTP
429with aRetry-Afterheader; you are never billed for overage. - The free Starter tier is rate-limited per IP address, includes an hourly anti-scraping cap, and adds a small fixed fairness delay to responses. Paid plans skip the delay; this difference is disclosed on the pricing page.
- We may apply additional temporary throttling to traffic patterns that degrade the service for others (for example, request floods or deliberate limit probing).
- If your application genuinely needs more than the published limits, contact us for a custom plan.
7. Acceptable use and data license
On a paid plan you may use the nutrition data in your own applications and services, including displaying, caching, and storing results your users request. You may not:
- Bulk-extract, crawl, or systematically copy the database in order to redistribute or resell it as a dataset or as a competing database or API;
- Use the free Starter tier for commercial products (it is intended for prototyping, evaluation, and non-commercial projects);
- Remove the required attribution described below;
- Attempt to bypass authentication, rate limits, or metering, or probe the service for vulnerabilities without written permission;
- Use the API in violation of applicable law.
Attribution requirement. Part of the database originates from Open Food Facts, which is licensed under the Open Database License (ODbL). That license requires attribution whenever the data is publicly used. If your application, website, or service publicly displays data obtained through the API, you must include a visible credit, on all plans including the free Starter plan, for example:
Food data from Open Food Facts (ODbL) via DietlyAPI
One line in a reasonable place is enough: near the displayed data, in an about or credits screen, or in your site footer. Link "Open Food Facts" to world.openfoodfacts.org where linking is possible. The "via DietlyAPI" part is appreciated but optional; the Open Food Facts credit is not. If you build a database that incorporates data from the API, the ODbL share-alike terms apply to the Open Food Facts portion of that database.
8. Data accuracy, AI content, and medical disclaimer
Nutrition values come from public databases, manufacturer data, community submissions, and machine-generated estimates. Entries carry confidence scores and AI-estimated entries are marked as such, but all values are estimates and may contain errors. You are responsible for how the data is used in your product. The API provides general nutrition information only; it is not a medical device and its output is not medical advice. Do not rely on it as the sole basis for medical or safety-critical decisions (for example allergen or dosage decisions).
9. Availability and changes
We aim for high availability and publish live uptime and latency on the status page, but self-serve plans do not include a guaranteed service level agreement. The service may be briefly interrupted by maintenance, upgrades, or events outside our control. We may evolve the API over time; for breaking changes to documented endpoints on paid plans we will give reasonable advance notice where practicable. If you need a contractual SLA, contact us about an Enterprise plan.
10. Suspension and termination
You can stop using the API and cancel your subscription at any time. We may suspend or terminate access if you materially breach these Terms (including non-payment or acceptable-use violations), with notice where reasonable. Sections that by their nature should survive (payment obligations, disclaimers, limitations of liability, governing law) survive termination.
11. Disclaimer of warranties
The API and its data are provided "as is" and "as available" without warranties of any kind, express or implied, including fitness for a particular purpose, non-infringement, and accuracy of nutritional data, to the maximum extent permitted by law.
12. Limitation of liability
To the maximum extent permitted by law, we are not liable for indirect, incidental, special, or consequential damages, or loss of data, revenue, or profits, arising from your use of the API. Our total liability for any claim is limited to the amount you paid us for the API in the 12 months before the claim arose. Nothing in these Terms excludes liability that cannot be excluded under applicable law.
13. Governing law
These Terms are governed by the laws of the Netherlands. If you are a consumer in the EU, you also benefit from mandatory provisions of the law of your country of residence, and you may bring disputes before the courts of that country. Contact API support first so we can try to resolve a dispute directly; this does not limit any right to use a competent alternative dispute-resolution body or court.
14. Changes to these Terms
We may update these Terms from time to time. The "Last updated" date at the top reflects the latest version; material changes will be announced on the site or by email to account holders. Continued use after changes take effect constitutes acceptance.
15. Contact
Questions about these Terms, billing, or refunds: [email protected]