API · /nationaldishes-api

National Dishes API

healthy 3,169 Subscribers

The dish most associated with each country as an API — a small, fun reference for travel, food, quiz and trivia apps. Built on the open country-json national-dish dataset and enriched with each country's ISO 3166-1 alpha-2 code and Unicode flag emoji. Look up a country's national dish by country name or code, search dishes and countries by keyword (for example, find every country whose national dish involves rice), or list them all. Served from memory — always fast.

api.oanor.com/nationaldishes-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/nationaldishes-api/openapi.json
/api/nationaldishes-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
112 ms
Server probes · 24h
Subscribers
3,169
active
Total calls
28
last 7 days
status Full status page → · 12 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 10,000 calls / month
  • 3 requests / second
  • Hard cap (429 above quota, no overage)
  • 10k calls/month
  • 3 req/sec
  • All endpoints
  • No credit card
Sign in to subscribe

Starter

€3.00 /month

  • 120,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 120k calls/month
  • 8 req/sec
  • Email support
Sign in to subscribe

Pro

€9.00 /month

  • 600,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 600k calls/month
  • 20 req/sec
  • Priority support
Sign in to subscribe

Mega

€22.00 /month

  • 3,000,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 3M calls/month
  • 50 req/sec
  • Dedicated SLA
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

Fruit Nutrition API

Fruit nutrition and botanical taxonomy as an API, built on the open Fruityvice dataset. Get every fruit with its scientific classification — family, genus and order — and its per-100g nutrition: calories, sugar, carbohydrates, protein and fat. Look up a single fruit by name, list every fruit in a botanical family (e.g. Rosaceae), genus (e.g. Prunus) or order (e.g. Rosales), or filter the whole catalogue by a nutrient range — for example all fruits with under 5g of sugar, sorted lowest first. Real data, no key needed upstream. Ideal for nutrition and diet apps, smoothie and recipe tools, health trackers and educational projects.

api.oanor.com/fruit-api

Jam & Preserve API

Jam and preserve maths as an API, computed locally and deterministically — the sugar, setting-point and yield numbers a jam maker, preserver or recipe app works a batch to. The sugar endpoint sets the sugar from the sugar-to-fruit ratio: a traditional full-sugar jam is 1:1, so 1 kg of fruit takes 1 kg of sugar for a 2 kg batch at 50 % sugar, while lower ratios (0.6–0.75) make a softer, fresher, less-sweet preserve that needs added pectin and keeps less well — the sugar both preserves and helps the gel. The setting-point endpoint gives the gel temperature adjusted for altitude: jam sets at about 4.5 °C (8 °F) above the temperature water boils at — 104.5 °C at sea level — but because water boils lower as you climb (roughly 1 °C per 285 m), the target falls to near 99 °C at 1500 m, so cooking to the sea-level figure up a mountain over-boils the batch. The yield endpoint boils the batch down to a target soluble-solids (Brix): jam keeps at about 65 % Brix, the finished weight = the solids (sugar plus the fruit's own ~10 % dry matter) ÷ the target Brix, and the rest evaporates as water — 1 kg sugar and 1 kg fruit boils down to about 1690 g of jam, losing roughly 310 g of water. Everything is computed locally and deterministically, so it is instant and private. Ideal for preserving and recipe tools, homestead and kitchen apps, and food-production calculators. Pure local computation — no key, no third-party service, instant. Gel chemistry, not canning safety. 3 compute endpoints. For processing-time altitude adjustment use a canning API.

api.oanor.com/jam-api

Ice Cream API

Ice-cream and gelato batch maths as an API, computed locally and deterministically — the overrun, yield and solids numbers a gelatiere, ice-cream maker or production planner balances a mix by. The overrun endpoint measures the air whipped into the mix during freezing by the weight method: from the same container filled first with mix and then with frozen ice cream, overrun = (mix weight − frozen weight) ÷ frozen weight × 100 — a cup that drops from 1000 g to 625 g ran 60 % overrun. Dense gelato sits around 20–35 %, premium ice cream 25–50 %, soft-serve and economy tubs 50–100 %+; more air means a lighter, cheaper, faster-melting product. The yield endpoint turns a mix volume and an overrun into the frozen volume (mix × (1 + overrun/100)) and the number of scoops at a given scoop size, so 2 litres of mix at 60 % overrun yields 3.2 litres and about 53 sixty-millilitre scoops — which is why overrun is a direct cost lever. The total-solids endpoint balances a recipe: total solids (sugar + fat + milk-solids-not-fat + other) as a percent of the mix weight, with the fat, sugar, MSNF and water percentages — a typical ice cream runs 36–42 % total solids, gelato lower in fat, and balancing solids against water is what keeps the texture smooth rather than icy. Everything is computed locally and deterministically, so it is instant and private. Ideal for gelateria and creamery tools, recipe-balancing apps, and food-production calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For general cooking measure conversions use a cooking API.

api.oanor.com/icecream-api

Cooking API

Recipe and kitchen conversions as an API. Convert between volume units (teaspoon, tablespoon, cup, fl-oz, ml, litre, pint, quart, gallon) and between mass units (gram, kilogram, ounce, pound) — and, crucially, between volume and mass for a specific ingredient using its density, so 1 cup of all-purpose flour ≈ 125 g, 1 cup of granulated sugar ≈ 200 g and 1 cup of water ≈ 237 g. 30 common ingredients are built in (flours, sugars, butter, oils, honey, rice, oats, cocoa, cornstarch and more), each with its grams-per-cup. Perfect for recipe apps, scaling and "metric vs cups" conversion, shopping lists and meal-prep tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from general physical unit conversion, which has no ingredient densities.

api.oanor.com/cooking-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for National Dishes API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call National Dishes API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for National Dishes API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does National Dishes API cost?
National Dishes API has a free tier with 100 calls / month. Paid plans start at €3.00 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is National Dishes API GDPR-compliant?
All requests to National Dishes API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/nationaldishes-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/nationaldishes-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/nationaldishes-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/nationaldishes-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.