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.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Yummly the way a machine reads it — 6 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Yummly scores 22.2/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Yummly
Each block below is one kind of artifact we hold for Yummly. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Yummly Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Yummly Rate Limits
RATE LIMITSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Yummly — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
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
← All providers · Data indexed from github.com/api-evangelist/yummly · machine-readable index on apis.io