Fruityvice Fruit Nutrition Scraper

Scrape Fruityvice — an open reference database of fruit nutrition and botanical classification. Pull the whole catalog, look up individual fruits by name, or list every fruit in a botanical family, and get calories, sugar, carbohydrates, protein and fat per 100 g alongside the fruit's family, order, and genus. Calorie and sugar range filters let you build low-sugar or high-energy shortlists in one run. HTTP-only via the public fruityvice.com API. No auth, no proxy.

What this actor does

• Three modes: all, byName, byFamily
• 19 botanical families exposed as a dropdown with plain-English hints (Rutaceae (citrus), Musaceae (bananas), …)
• Nutrition range filters: min/max calories and min/max sugar per 100 g
• Flat and nested nutrition: every value is available as a top-level field and inside a nutritions object
• Empty fields are omitted

Output per fruit

• fruitId — Fruityvice numeric ID
• name — common fruit name
• family — botanical family (e.g. Rosaceae)
• order — botanical order (e.g. Rosales)
• genus — botanical genus (e.g. Malus)
• calories — kcal per 100 g
• sugar — grams per 100 g
• carbohydrates — grams per 100 g
• protein — grams per 100 g
• fat — grams per 100 g
• nutritions — the same values nested as calories, sugarG, carbohydratesG, proteinG, fatG
• recordType: "fruit", scrapedAt

Input

Field	Type	Default	Description
mode	string	all	all / byName / byFamily
fruitName	string	apple	Single fruit to look up (mode=byName)
fruitNames	array	–	Multiple fruits to look up (mode=byName)
family	string	–	Botanical family (required for byFamily, optional filter for all)
minCalories	number	–	Keep fruits with at least this many kcal per 100 g (mode=all)
maxCalories	number	–	Keep fruits with at most this many kcal per 100 g (mode=all)
minSugar	number	–	Keep fruits with at least this much sugar per 100 g (mode=all)
maxSugar	number	–	Keep fruits with at most this much sugar per 100 g (mode=all)
maxItems	int	200	Hard cap (1–500)

Example: the whole catalog

{
  "mode": "all",
  "maxItems": 200
}

Example: low-sugar fruits

{
  "mode": "all",
  "maxSugar": 5,
  "maxItems": 50
}

Example: every citrus fruit

{
  "mode": "byFamily",
  "family": "Rutaceae"
}

Example: look up specific fruits

{
  "mode": "byName",
  "fruitNames": ["apple", "mango", "banana", "kiwi"]
}

Use cases

• Nutrition & diet apps — seed a food database with per-100 g macros for common fruits
• Recipe platforms — attach calorie and sugar data to fruit ingredients automatically
• Low-sugar and keto tooling — generate compliant fruit shortlists with the sugar filter
• Edtech & science content — teach botanical classification with family / order / genus data
• Grocery and meal-kit catalogs — enrich fruit SKUs with nutrition facts
• Chatbots & assistants — answer "how much sugar is in a mango?" from structured data

FAQ

What is Fruityvice? A free, open API serving nutritional and botanical data for common fruits. See fruityvice.com.

Is this affiliated with Fruityvice? No. This is a third-party actor using their public API.

Do I need an API key? No. The endpoints are open and unauthenticated.

How many fruits are in the catalog? Around 60 — common, widely eaten fruits rather than an exhaustive botanical index. It grows slowly.

What units are the nutrition values in? Everything is per 100 g of edible fruit: calories in kcal, and sugar, carbohydrates, protein, fat in grams.

Why does the record repeat nutrition data twice? The top-level fields (calories, sugar, …) are the convenient flat form for spreadsheets and SQL. The nutritions object preserves the grouped shape for consumers that already expect it.

Do the calorie and sugar filters work in every mode? They apply when browsing with mode: "all". In byName and byFamily the actor returns exactly what you asked for without additional filtering.

Why does filtering drop fruits with missing values? A fruit with no recorded calorie figure can't be proven to satisfy a calorie threshold, so it's excluded rather than guessed at.

Are the botanical names authoritative? They follow standard classification, but a handful of families (for example Punicaceae) have been merged elsewhere in modern taxonomy. The actor reports what the source publishes.

How fresh is the data? Live — each run queries the API directly, though the underlying reference data changes rarely.