Chomp API

by chompthis.com

Overview

Data about various grocery products and foods

Chomp is a food & drink API from chompthis.com. Requests are authenticated with an API key. It is served over HTTPS. Its OpenAPI description documents 4 endpoints.

At a glance

Authentication: API key
HTTPS: Yes
CORS: Unknown
Category: Food & Drink
Base URL: https://chompthis.com/api/v2
Version: 1.0.0-oas3
Endpoints: 4
OpenAPI: Specification ↗
Spec updated: 2021-06-21

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL

curl -X GET "https://chompthis.com/api/v2/food/branded/barcode.php" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY"

JavaScript

const response = await fetch("https://chompthis.com/api/v2/food/branded/barcode.php", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "X-API-Key": "YOUR_API_KEY",
  },
});
const data = await response.json();
console.log(data);

Python

import requests

response = requests.request(
    "GET",
    "https://chompthis.com/api/v2/food/branded/barcode.php",
    headers={
    "Accept": "application/json",
    "X-API-Key": "YOUR_API_KEY",
    },
    timeout=30,
)
print(response.json())

Endpoints

Method	Path	What it does
GET	`/food/branded/barcode.php`	Get a branded food item using a barcode
GET	`/food/branded/name.php`	Get a branded food item by name
GET	`/food/branded/search.php`	Get data for branded food items using various search parameters
GET	`/food/ingredient/search.php`	Get raw/generic food ingredient item(s)

Questions

Does the Chomp API need an API key?

Yes. The Chomp API uses API key authentication; the documentation explains how to get credentials.

Does the Chomp API support HTTPS?

Yes, the Chomp API is served over HTTPS.

How many endpoints does the Chomp API have?

Its OpenAPI description lists 4 endpoints in version 1.0.0-oas3. All of them are shown on this page.

What are alternatives to the Chomp API?

Other Food & Drink APIs include Open Food Facts, Spoonacular, 1,000,000+ Recipe and Grocery List API (v2), Edamam nutrition, CalorieNinjas.

Compare alternatives →

Open Food Facts

Food & Drink

Food Products Database

No auth

Spoonacular

Food & Drink

Recipes, Food Products, and Meal Planning

API key99 endpoints

1,000,000+ Recipe and Grocery List API (v2)

Food & Drink

#Documentation This is the documentation for the partner endpoint of the BigOven Recipe and Grocery List API. The update brings with it Swagger-based documentation. [Swagger](http://swagger.io) is an emerging standard for describing REST-based APIs, and with this Swagger-compliant endpoint (above), you can make ready-to-go interface libraries for your code via [swagger-codegen](https://github.com/swagger-api/swagger-codegen). For instance, it's easy to generate libraries for Node.js, Java, Ruby, ASP.NET MVC, jQuery, php and more! You can also try out the endpoint calls with your own api_key right here on this page. Be sure to enter your api_key above to use the "Try it out!" buttons on this page. ##Start Here Developers new to the BigOven API should start with this version, not with the legacy API. We'll be making improvements to this API over time, and doing only bug fixes on the v1 API. To pretend you're a BigOven user (for instance, to get your recently viewed recipes or your grocery list), you need to pass in Basic Authentication information in the header, just as with the v1 API. We do now require that you make all calls via https. You need to pass your api_key in with every call, though this can now be done on the header (send a request header "X-BigOven-API-Key" set to your api_key value, e.g., Request["X-BigOven-API-Key"]="your-key-here".) ##Migration Notes For existing partners, we encourage you to [migrate](https://api2.bigoven.com), and while at this writing we have no hard-and-fast termination date for the v1 API, we strongly prefer that you migrate by January 1, 2017. While the changes aren't overly complex, there are several breaking changes, including refactoring of recipe search and results and removal of support for XML. This is not a simply plug-and-play replacement to the v1 API. With respect to an exclusive focus on JSON, the world has spoken, and it prefers JSON for REST-based API's. We've taken numerous steps to refactor the API to make it more REST-compliant. Note that this v2 API will be the preferred API from this point onward, so we encourage developers to migrate to this new format. We have put together some [migration notes](/web/documentation/migration-to-v2) that we encourage you to read carefully. ##Photos See our [photos documentation](https://api2.bigoven.com/web/documentation/recipe-images). For more information on usage of this API, including features, pricing, rate limits, terms and conditions, please visit the [BigOven API website](https://api2.bigoven.com).

API key66 endpoints