Foodashi is a Recipe & Food Data API built for developers. It provides AI-generated recipes, ingredient lists, nutritional estimates, allergen indicators, cooking instructions, and food imagery. Use it to power recipe apps, meal planners, food blogs, restaurant tools, and more. Our API runs on Cloudflare's global edge network for fast responses worldwide.

Getting started takes under 2 minutes:

1. Create a free account (no credit card required).
2. Log in to the Developer Console and generate your API key.
3. Try the Test Kitchen to explore recipes in your browser — no code needed.
4. Make your first API call using the X-Api-Key header.
5. Read the API Documentation for all endpoints, parameters, and examples.

The free Hobby plan gives you 10,000 requests per month to build and test your integration.

Yes! The Hobby plan is completely free and includes:

• 10,000 requests per month
• 30 requests per minute (RPM)
• 1 API key
• 22 core endpoints — recipe browsing, ingredient search, nutrition reference, and utilities
• Access to the Test Kitchen

No credit card is required. The Hobby plan is for non-commercial use only (personal projects, testing, evaluation). For commercial use, upgrade to Indie ($25/mo), Pro ($90/mo) for AI features, or Enterprise.

The Test Kitchen is a browser-based tool that lets you explore Foodashi's recipe data without writing code. Search for recipes, view ingredient details, nutritional info, and allergen data — all through a visual interface. It's perfect for evaluating the API before integrating it into your application. Available on all plans including Hobby.

No. You can create a free Hobby account and start using the API immediately without entering any payment information. A credit card is only required when you upgrade to a paid plan (Indie, Pro, or Enterprise).

We offer four plans to fit any project size. All prices are in USD:

Plan	Price	Requests/mo	RPM	API Keys
Hobby	Free	10,000	30	1
Indie	$25/mo	150,000	600	3
Pro	$90/mo	1,000,000	3,000	10
Enterprise	Custom	10,000,000+	10,000+	Unlimited

Yearly billing is available — get 2 months free (Indie $250/yr, Pro $900/yr). See the Pricing page for full details and feature comparison.

Paid plans are billed on a monthly or yearly subscription via Stripe. Your card is charged automatically at the start of each billing period. You can view invoices, manage your subscription, and change plans from the Developer Console. All prices are in USD.

We accept all major credit and debit cards (Visa, Mastercard, American Express) via Stripe. We also support iDEAL and SEPA Direct Debit for European customers. We never store your card details — all payment processing is handled securely by Stripe.

When you reach your plan's monthly request limit, additional requests will return a 429 Too Many Requests error until your limit resets on the 1st of each month (00:00 UTC).

Indie and Pro plans can turn on extra usage in the Developer Console and keep a prepaid balance (topped up by hand or with optional automatic top-ups). Requests beyond your plan are then paid from that balance at $0.50 per 1,000 credits on Indie and $0.30 on Pro instead of being blocked. Unspent balance is refunded when you move to Hobby or delete your account, minus the card processing fee. Most endpoints consume 1 credit per call; search, bulk lookups and the nutrition calculators use 2 to 5 credits, and AI-powered endpoints (cooking tips, photo recognition, recipe analysis, meal plan generation) use 65 to 400 credits. Full per-endpoint costs are shown in the documentation and Test Kitchen.

Hobby plan users must upgrade to increase their limits; extra usage is not available on Hobby.

Yes, you can change plans at any time from the Developer Console:

Upgrades take effect immediately. You get instant access to higher limits and your billing is adjusted.

Downgrades take effect at the end of your current billing period. You keep your current plan's limits until then, so you never lose access to time you've already paid for.

Yes, cancel anytime from the Developer Console. You have two options:

Turn off auto-renewal: Your access continues until the end of the current billing period, then downgrades to the free Hobby plan.

Cancel with refund (if eligible): Your subscription ends immediately and you receive a full or pro-rata refund based on when you were last charged and how much you have used. See our Refund Policy for eligibility windows.

Refunds are processed automatically from the Developer Console (no support ticket needed). Your first payment and each renewal open a refund window:

Within 24 hours → full refund and immediate cancellation, as long as you have used 5% or less of the plan and made no AI-powered requests.
Days 2 to 14 → a refund of the share you have not used (time or requests, whichever is higher) and immediate cancellation.
After 14 days → no refund; cancel at end of billing period.
Prepaid usage credit → the unspent balance is refunded when you move to Hobby or delete your account, minus the card processing fee.

Refund amounts are based on what you actually paid (after any coupons or discounts). See the full Refund & Cancellation Policy.

If your subscription auto-renewed unexpectedly, you can cancel with a full refund within 24 hours of the renewal charge (if you have used 5% or less and made no AI-powered requests since it), or get back the share you have not used within 14 days. Go to the Developer Console and click "Cancel Subscription".

To prevent future surprise renewals, toggle off auto-renewal in the Developer Console before your next billing date.

Click "Forgot your password?" on the login page. Enter your email address and you'll receive a password reset link. The link expires after 24 hours. If you don't see the email, check your spam/junk folder.

Log in to the Developer Console to create, view, rename, or revoke API keys. The number of active keys depends on your plan:

• Hobby: 1 key
• Indie: up to 3 keys
• Pro: up to 10 keys
• Enterprise: unlimited keys

Revoking a key is instant and irreversible — any application using that key will immediately lose access. You can generate a new key to replace it.

Common reasons an API key returns errors:

• Key is revoked or expired — check the Developer Console to confirm your key is active.
• Wrong header — use X-Api-Key (not Authorization).
• Monthly limit reached — check your usage in the Console. You'll get a 429 error.
• Rate limit (RPM) exceeded — slow down requests. You'll get a 429 error with a Retry-After header.
• Account suspended — check your email for a notice from Foodashi.

If none of these apply, contact support with your API key prefix (first 8 characters only — never share the full key).

Currently, email changes are not self-service. Please contact us from your registered email address and we'll update it for you. Your API keys and billing will transfer automatically.

You can delete your account from the Developer Console under Account Settings. Deleting your account will:

• Permanently revoke all your API keys (immediate)
• Cancel any active subscription
• Delete your customer record and usage data

This action is irreversible. If you have an active paid subscription, consider cancelling and requesting a refund first (if eligible). Deleting your account refunds any unspent prepaid usage credit (minus the card processing fee), but not a subscription payment.

The Developer Console shows your real-time usage including:

• Requests used this billing period vs. your monthly limit
• Current plan tier and billing date
• Active API keys and their individual usage
• Subscription status and renewal date

Usage data updates in near real-time.

Include your API key in the X-Api-Key header with every request:

X-Api-Key: your_api_key_here

Never expose your API key in client-side code, public repos, or any publicly accessible location. If you suspect a key has been compromised, revoke it immediately in the Developer Console and generate a new one.

Each plan has both a monthly request quota and a per-minute rate limit (RPM):

Plan	Monthly Limit	RPM
Hobby	10,000	30/min
Indie	150,000	600/min
Pro	1,000,000	3,000/min
Enterprise	10,000,000+	10,000/min

When either limit is hit, you'll receive a 429 Too Many Requests response. Monthly limits reset at the start of your billing period. RPM limits reset every 60 seconds.

All API responses are in JSON format. Every response includes structured fields for recipe data, nutritional information, allergen indicators, and metadata. Refer to the API Documentation for detailed schemas and example responses.

Yes. Foodashi provides a RESTful API accessible via standard HTTPS requests. All endpoints return JSON. The API is hosted on Cloudflare's global edge network, providing low-latency responses worldwide with built-in DDoS protection.

Limited, short-term caching for performance is permitted. However, you must not persistently cache, mirror, or index responses in a way that bypasses usage limits, creates a derivative database, or eliminates the need for future API calls. See the API License Agreement for full caching rules.

Foodashi targets high availability but does not guarantee 100% uptime. If the API is temporarily unavailable, requests may return a 503 response. We recommend implementing retry logic with exponential backoff in your application. We do not offer SLA-backed uptime guarantees on Hobby, Indie, or Pro plans. Enterprise customers can negotiate custom SLAs — contact us for details.

Not yet — but the API is a standard REST API, so you can use it with any HTTP client in any language (Python requests, JavaScript fetch, Go net/http, etc.). Check the Documentation for code examples in popular languages.

The Test Kitchen serves as an interactive sandbox where you can test queries and explore results in your browser. For API-level testing, use your Hobby plan key — it provides 10,000 free requests per month, which is sufficient for prototyping. All plans use the same production API; there is no separate staging environment.

Yes. Recipes, cooking steps, and food imagery are generated by artificial intelligence, and nutrition and allergen data are derived from them automatically, partly with AI estimates. Content may contain inaccuracies or omissions. If you show it to your users, keep our AI markers, make it clear the content is AI-generated, and follow the other safeguards in our API License Agreement. No per-recipe human review is required.

Nutritional data (calories, macronutrients, etc.) is estimated: calculated from national food composition databases and, where no measured value exists, from AI estimates recorded at lower confidence. Actual values vary with specific ingredients, brands, preparation methods, and portion sizes. Present figures as estimates, and verify them independently before using them for medical, dietary, or food labeling purposes.

No. All allergen information is automatically generated by AI and may be incomplete, inaccurate, or missing critical allergens. Allergen indicators do not account for cross-contamination, ingredient substitutions, or manufacturer-specific formulations.

Do not use Foodashi allergen data as the sole source for allergen decisions. Show allergen information as indicative, remind your users to check ingredients and product labels, and never describe a recipe as allergy-safe on the basis of our data alone. See our Terms of Service (Section 5) for full details.

Recipes are AI-generated and can contain mistakes, such as incorrect cooking temperatures, unsafe food combinations, missing safety steps, or inaccurate preparation instructions. When cooking, use your own judgement and check cooking temperatures against authoritative food safety guidance (for example USDA or the UK Food Standards Agency). Apps that show our recipes should make this clear to their users.

No. Apps and websites can show recipes automatically, without reviewing each one, as long as they keep the safeguards in our API License Agreement: make AI generation clear, present nutrition as estimates and allergens as indicative, make no medical or allergy-safety claims, and let users report errors. Higher-risk uses, such as clinical nutrition, infant feeding, allergen control in food businesses, food labels, and printed cookbooks presented as tested, need a qualified person to review content first. See our Acceptable Use Policy.

No. Foodashi is not a medical, nutritional, or dietary authority. You must not use API data as the sole basis for managing medical conditions (diabetes, celiac disease, food allergies, etc.), creating clinical meal plans, or providing dietary advice without oversight from a licensed healthcare provider. See our Acceptable Use Policy.

Recipes are AI-generated. Foodashi does not claim copyright ownership over AI-generated outputs and makes no representation regarding their intellectual property status. AI-generated content may not be eligible for copyright protection under applicable law. You are responsible for conducting IP due diligence before publishing or commercialising API content.

Yes, on Indie, Pro, and Enterprise plans, for almost any kind of app, including meal planners, grocery apps, and cooking apps. The Hobby (free) plan is for non-commercial, personal use. No Foodashi branding is required, but the open databases our nutrition data comes from must be credited (a link to our Data Sources page is enough), and you must follow the safeguards in our API License Agreement. You may not resell the data or build a data product from it.

Foodashi provides informational data only and does not guarantee compliance with any food labeling regulation. If you use API data for food labels, menus for sale, or other regulated food information, you are responsible for compliance with the applicable regulations (EU Regulation 1169/2011, US FALCPA/FASTER Act, UK Natasha's Law, etc.) and must verify the data independently first.

Your use of Foodashi is governed by:

1. Terms of Service — general terms, liability, disclaimers
2. API License Agreement — developer-specific API usage rules
3. Privacy Policy — how we collect and process data
4. Refund & Cancellation Policy — refund windows and cancellation rules
5. Acceptable Use Policy — prohibited and restricted uses

Yes. If your application displays Foodashi-generated content to end users, you must:

• On the Hobby plan, show a "Powered by Foodashi" link (Indie and Pro need no Foodashi branding)
• Disclose that content is AI-generated and has not been professionally verified (unless you have verified it)
• Display appropriate warnings about allergens, nutritional accuracy, and food safety
• Not represent AI-generated content as human-authored without independent verification

Foodashi is built to meet GDPR, UK GDPR and CCPA/CPRA requirements: we process minimal personal data, do not sell it, do not use advertising cookies, and never use API payloads to train machine learning models. Our Privacy Policy and Data Processing Agreement describe exactly what is processed and why.

No. Foodashi does not use customer API payloads, search terms, or account data to train proprietary machine learning models. Your data is processed solely to fulfil API requests and for legitimate platform operations (security, billing, abuse prevention).

Our Terms of Service are governed by the laws of England and Wales. EU consumers retain the right to bring proceedings in their country of residence under applicable consumer protection laws. Nothing in our terms overrides statutory consumer rights that cannot be waived by contract.

You can delete your account and data directly from the Developer Console. Alternatively, email us via the contact page and we'll process your request within 30 days. Note that certain data (e.g., billing records) may be retained for up to 7 years to meet tax and legal obligations, as detailed in our Privacy Policy.