Tastewise API

Commercial REST API over the Tastewise food and beverage intelligence graph. Publicly documented operations span recipes (popular/trending), ingredients, dishes and side dishes, restaurants (search, detail, menus, ingredients, signals, bestsellers, price analysis, chain matching), menus and menu insights, consumer motivations, social content discovery, flavor combinations, trend validation and trend performance, a combined insights endpoint, an embedded widgets query surface, and product-list management with bulk import and webhook completion callbacks. Authentication is a bearer API key paired with an X-Customer-Id header, and each route requires a named permission on the account. No machine-readable OpenAPI is published; the reference is human-readable Slate documentation.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/tastewise-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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

API entry from apis.yml

apis.yml Raw ↑
aid: tastewise:tastewise-api
name: Tastewise API
description: Commercial REST API over the Tastewise food and beverage intelligence graph. Publicly documented
  operations span recipes (popular/trending), ingredients, dishes and side dishes, restaurants (search,
  detail, menus, ingredients, signals, bestsellers, price analysis, chain matching), menus and menu insights,
  consumer motivations, social content discovery, flavor combinations, trend validation and trend performance,
  a combined insights endpoint, an embedded widgets query surface, and product-list management with bulk
  import and webhook completion callbacks. Authentication is a bearer API key paired with an X-Customer-Id
  header, and each route requires a named permission on the account. No machine-readable OpenAPI is published;
  the reference is human-readable Slate documentation.
humanURL: https://docs.tastewise.io/
baseURL: https://api.tastewise.io
tags:
- Food and Beverage
- Consumer Insights
- Restaurant
- Menus
- Recipes
- Trends
tags_raw:
- Food and Beverage
- Consumer Insights
- Restaurants
- Menus
- Recipes
- Trends
properties:
- type: APIReference
  url: https://docs.tastewise.io/
- type: Authentication
  url: authentication/tastewise-authentication.yml
- type: RateLimits
  url: rate-limits/tastewise-rate-limits.yml
- type: ErrorCatalog
  url: errors/tastewise-problem-types.yml
- type: Conventions
  url: conventions/tastewise-conventions.yml
- type: Webhooks
  url: asyncapi/tastewise-webhooks.yml