Food Database API

Name: Food Database API API
Brand: Food Database API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationnone4 EndpointsREST

For Agents

Search Edamam's foods database, look up full nutrition by foodId or image, and power autocomplete for food search via four REST endpoints.

Quickstart

Get started with Food Database API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"parse food query and get edamam nutrition"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Food Database API API.

Parse a free-text food query into matching Edamam foodIds with portion measures

Look up full nutrition for a chosen foodId and quantity via the nutrients endpoint

Run a beta nutrition lookup from a meal image to extract nutrient totals

Provide autocomplete suggestions for food search inputs

GET STARTED

Start building with Food Database API API

Explore with Jentic

View OpenAPI Document

Use for: Parse 'one cup of cooked rice' into an Edamam foodId, Look up full nutrition for a specific Edamam foodId at a given quantity, Get nutrition data from a photo of a meal using the beta image endpoint, Provide autocomplete suggestions for the food search query 'apple'

Not supported: Does not handle recipe analysis, meal planning, or shopping list generation — use for Edamam food search, nutrient lookup, image-based nutrition (beta), and autocomplete only.

Jentic publishes the only available OpenAPI document for Food Database API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Food Database API, keeping it validated and agent-ready. The Edamam Food Database API converts free-text food queries and grocery items into structured nutrition data drawn from a curated foods database. It exposes a parser endpoint for food search, nutrient lookup endpoints for full nutrition retrieval (including a beta image-based lookup), and an autocomplete endpoint to power search-as-you-type interfaces. Health, fitness, and recipe applications use it to attach nutrition facts to user-entered foods without maintaining their own food taxonomy.

Use Cases

Patterns agents use Food Database API API for, with concrete tasks.

★ Meal Logging Nutrition Lookup

Diet and fitness apps let users enter foods in natural language and need to attach nutrition facts to each entry. The Food Database API's GET /api/food-database/v2/parser turns the user's query into Edamam foodIds with portion measures, then POST /api/food-database/v2/nutrients returns the full nutrient breakdown for the chosen quantity. The pair covers the parse-then-resolve flow most meal trackers depend on.

GET /api/food-database/v2/parser for the user's food entry, pick the closest match, then POST /api/food-database/v2/nutrients for the chosen quantity.

Search-As-You-Type Food Pickers

Food pickers and grocery search inputs benefit from low-latency autocomplete. GET /auto-complete returns suggestion strings for a partial query, which the client can render below the input. This is independent of the parser flow — it suggests text, not foodIds — so it works as a thin layer on the front end.

Call GET /auto-complete on every keystroke after two characters and render the returned suggestions in the picker dropdown.

AI Vision Meal Estimation (Beta)

POST /api/food-database/nutrients-from-image is a beta endpoint that takes a meal image and returns nutrient estimates. Apps offering 'snap-and-track' meal logging use it as a drop-in for users who don't want to type every food. The endpoint is in beta so production apps usually allow a manual confirmation step before persisting the values.

POST /api/food-database/nutrients-from-image with the meal photo, present the estimated foods to the user, and let them confirm before logging.

AI Agent Nutrition Assistant

An AI agent built into a wellness app can use Jentic to discover the parser, nutrients, and autocomplete endpoints and chain them into a 'log my meal' flow. The agent parses the user's prompt, picks the best foodId match, calls the nutrients endpoint for full breakdown, and writes the result back to the user's diary, all without a custom Edamam integration.

Through Jentic, search 'parse food and get nutrition', load the parser and nutrients schemas, and execute the chained call for 'two slices of whole wheat toast'.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for food database api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/food-database/v2/parser

Search foods and return foodIds with measures

POST

/api/food-database/v2/nutrients

Full nutrition lookup by foodId and quantity

POST

/api/food-database/nutrients-from-image

Beta nutrition lookup from a meal image

GET

/auto-complete

Autocomplete suggestions for food search

GET

/api/food-database/v2/parser

Search foods and return foodIds with measures

POST

/api/food-database/v2/nutrients

Full nutrition lookup by foodId and quantity

POST

/api/food-database/nutrients-from-image

Beta nutrition lookup from a meal image

GET

/auto-complete

Autocomplete suggestions for food search

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Edamam app_id and app_key are stored encrypted in the Jentic vault. Agents receive operations and Jentic injects both query parameters at call time so the raw credentials never enter the agent's context or logs.

Intent-based discovery

Agents search natural-language intents like 'parse food and get nutrition' and Jentic returns the matching parser and nutrients operations with their input schemas, so the agent calls the right endpoint without reading the Edamam developer portal.

Time to first call

Direct Edamam integration takes 1-2 days to chain parser to nutrients, handle the beta image endpoint, and account for the app_id/app_key query-parameter pattern. Through Jentic the search-load-execute flow is under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Spoonacular API

Broader recipes-and-nutrition platform covering meal planning beyond Edamam's food database

Choose Spoonacular when the agent needs recipes, meal planning, or restaurant menu data on top of nutrition lookups.

Alternative

Nutritionix API

Natural-language nutrition lookup with restaurant and grocery brand coverage

Choose Nutritionix when restaurant chain coverage matters more than Edamam's general foods database.

Complementary

CROssBAR Data API

Biomedical reference data for research workflows that pair with nutrition lookups

Use CROssBAR when the workflow extends into biomedical research (drugs, proteins) alongside nutrition data from Edamam.

FAQs

Specific to using Food Database API API through Jentic.

Why is there no official OpenAPI spec for Food Database API?

Edamam does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Food Database API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Edamam Food Database API use?

The Edamam Food Database API uses an app_id and app_key pair as API key credentials. Through Jentic, both values are stored encrypted in the Jentic vault and injected into the request at call time so the raw key never enters the agent's context.

Can I get nutrition data for a free-text food query with the Food Database API?

Yes. GET /api/food-database/v2/parser turns a free-text query into matching foodIds with portion measures, and POST /api/food-database/v2/nutrients returns the full nutrient breakdown for a chosen foodId and quantity.

What are the rate limits for the Edamam Food Database API?

The OpenAPI spec does not declare rate limits. Edamam applies plan-based call quotas tied to the app_id; the parser, nutrients, and autocomplete endpoints share that pool, so cache parser results and reuse foodIds to keep call volume down.

How do I run the beta image nutrition endpoint through Jentic?

Search 'edamam nutrition from image' in Jentic, load the POST /api/food-database/nutrients-from-image schema, send the image payload, and Jentic returns the estimated foods and nutrients. The endpoint is in beta so allow user confirmation before persisting values.

Does the Food Database API include recipe analysis?

No. This spec covers food search, nutrient lookup, image-based nutrition, and autocomplete only. Recipe-level analysis is provided by Edamam's separate Recipe Search and Nutrition Analysis APIs.