Yummly website screenshot

Yummly

Yummly is a recipe and food discovery platform (yummly.com) offering semantic and visual recipe search, personalized recommendations, shopping lists, and guided cooking. Founded in 2009 (Redwood City, CA), Yummly was acquired by Whirlpool Corporation in May 2017 and operated as a wholly owned subsidiary tied to Whirlpool's smart-kitchen strategy. Yummly historically ran a well-known public Recipe API (developer.yummly.com) exposing recipe search, recipe details, and metadata endpoints. That developer program was DEPRECATED - it stopped accepting new signups and was wound down (commonly cited end date of September 30, 2019), and the developer.yummly.com developer portal and api.yummly.com endpoints are no longer available. There is no public Yummly developer API accepting new registrations as of this cataloging (2026-07-03); the APIs below are documented as historical / modeled for archival and migration reference only.

Yummly is listed with 3 APIs on the APIs.io network. Tagged areas include Recipes, Food, Cooking, Recipe Search, and Food Discovery.

Yummly’s developer surface includes documentation and 5 more developer resources.

9.5/100 minimal ▬ flat Agent 1/100 human only saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
AccessFreemiumFree trial
3 APIs
RecipesFoodCookingRecipe SearchFood DiscoveryDeprecatedHistorical

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Yummly It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/yummly/"><img src="https://apis.io/badge/yummly/card.svg" alt="Yummly on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
  • Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
12 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Yummly · a person reads this and replies by email.
or email info@apis.io
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/yummly/apis.yml: open an issue on github.com/api-evangelist/yummly to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Yummly Recipe Search API (Historical)

DEPRECATED / HISTORICAL. The Search Recipes endpoint (GET http://api.yummly.com/v1/api/recipes) returned recipe matches as JSON with optional filters combined via AND - free-tex...

Yummly Recipe Details API (Historical)

DEPRECATED / HISTORICAL. The Get Recipe endpoint (GET http://api.yummly.com/v1/api/recipe/{recipe-id}) returned the full detail for a single recipe by its Yummly recipe id - ing...

Yummly Metadata API (Historical)

DEPRECATED / HISTORICAL. The Metadata endpoints (GET http://api.yummly.com/v1/api/metadata/{key}) returned the controlled vocabularies used to build search filters - keys includ...

Yummly API pricing

Not yet checked against Yummly's own pricing page. Compiled by API Evangelist on 2026-07-03 from developer.yummly.com/plans; confirm before you rely on a figure. A free plan or tier is listed.

PlanPrice
Free (Evaluation) free —
Lite (Paid) paid —
Plus (Paid) paid —
Custom / Enterprise enterprise —

Plan details, limits and sources →

Rate limits

Compiled by API Evangelist, not yet checked against Yummly's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Yummly Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Yummly Rate Limits

4 limits

RATE LIMITS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Yummly Domain Security

TLSv1.2

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: yummly
url: https://raw.githubusercontent.com/api-evangelist/yummly/refs/heads/main/apis.yml
name: Yummly
kind: company
description: Yummly is a recipe and food discovery platform (yummly.com) offering semantic and visual recipe search, personalized
  recommendations, shopping lists, and guided cooking. Founded in 2009 (Redwood City, CA), Yummly was acquired by Whirlpool
  Corporation in May 2017 and operated as a wholly owned subsidiary tied to Whirlpool's smart-kitchen strategy. Yummly historically
  ran a well-known public Recipe API (developer.yummly.com) exposing recipe search, recipe details, and metadata endpoints.
  That developer program was DEPRECATED - it stopped accepting new signups and was wound down (commonly cited end date of
  September 30, 2019), and the developer.yummly.com developer portal and api.yummly.com endpoints are no longer available.
  There is no public Yummly developer API accepting new registrations as of this cataloging (2026-07-03); the APIs below are
  documented as historical / modeled for archival and migration reference only.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: true
  try_now: false
  public: false
  label: Freemium (free trial)
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/yummly.png
tags:
- Recipes
- Food
- Cooking
- Recipe Search
- Food Discovery
- Deprecated
- Historical
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: yummly:yummly-recipe-search-api
  name: Yummly Recipe Search API (Historical)
  tags:
  - Recipe Search
  - Search
  - Deprecated
  - Historical
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.yummly.com/documentation.html
  baseURL: http://api.yummly.com/v1/api
  properties:
  - url: https://developer.yummly.com/documentation.html
    type: Documentation
  - url: https://developer.yummly.com/
    type: APIReference
  description: DEPRECATED / HISTORICAL. The Search Recipes endpoint (GET http://api.yummly.com/v1/api/recipes) returned recipe
    matches as JSON with optional filters combined via AND - free-text query (q), maxResult / start paging, and facets such
    as allowedIngredient/excludedIngredient, allowedCuisine, allowedCourse, allowedAllergy, allowedDiet, allowedHoliday, maxTotalTimeInSeconds,
    and nutrition/taste ranges. Authenticated with _app_id and _app_key query parameters. This endpoint and the developer.yummly.com
    program are no longer available; endpoint modeled from historical documentation and community client libraries.
- aid: yummly:yummly-recipe-details-api
  name: Yummly Recipe Details API (Historical)
  tags:
  - Recipe Details
  - Recipe
  - Deprecated
  - Historical
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.yummly.com/documentation.html
  baseURL: http://api.yummly.com/v1/api
  properties:
  - url: https://developer.yummly.com/documentation.html
    type: Documentation
  description: DEPRECATED / HISTORICAL. The Get Recipe endpoint (GET http://api.yummly.com/v1/api/recipe/{recipe-id}) returned
    the full detail for a single recipe by its Yummly recipe id - ingredient lines, nutrition estimates, flavor/taste profile,
    total cooking time, source attribution, and image URLs. Authenticated with _app_id and _app_key query parameters. No longer
    available; endpoint modeled from historical documentation and community client libraries.
- aid: yummly:yummly-metadata-api
  name: Yummly Metadata API (Historical)
  tags:
  - Metadata
  - Taxonomy
  - Deprecated
  - Historical
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.yummly.com/documentation.html
  baseURL: http://api.yummly.com/v1/api
  properties:
  - url: https://developer.yummly.com/documentation.html
    type: Documentation
  description: DEPRECATED / HISTORICAL. The Metadata endpoints (GET http://api.yummly.com/v1/api/metadata/{key}) returned
    the controlled vocabularies used to build search filters - keys included ingredient, allergy, diet, cuisine, course, holiday,
    technique, source, brand, and restriction. Used to populate valid facet values for the Search Recipes endpoint. No longer
    available; endpoints modeled from historical documentation and community client libraries.
common:
- type: DomainSecurity
  url: security/yummly-domain-security.yml
- type: Website
  url: https://www.yummly.com
- type: LinkedIn
  url: https://www.linkedin.com/company/yummly
- type: Documentation
  url: https://developer.yummly.com/documentation.html
- type: Plans
  url: plans/yummly-plans-pricing.yml
- type: RateLimits
  url: rate-limits/yummly-rate-limits.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-status: acquired
x-parent: whirlpool
x-relationship: acquisition
x-acquired: 2017

Yummly API — frequently asked questions

Does Yummly have an API?

Yes. APIs.io lists 3 APIs from Yummly, including Yummly Recipe Search API (Historical), Yummly Recipe Details API (Historical) and Yummly Metadata API (Historical).

How much does the Yummly API cost?

APIs.io lists 4 pricing plans for Yummly, with each plan's price, limits and inclusions under Pricing on this page.

Is the Yummly API ready for AI agents?

Yummly has a Kin Score of 9.5 out of 100 (minimal) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/yummly"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/yummly/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/yummly/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.