What you can build with January
Start with food.
Build what comes next.
Discover restaurant menus Find a different fit.
Use a food ID to find healthier alternatives, with diet preferences and ingredient exclusions.
POST /v1.2/foods/{food_id}/alternativesTry with a saved food example →Add another perspective.
Combine food IDs, servings and amounts with a user profile, time and timezone to predict a glucose response.
POST /v1.2/glucose/predictionsStart from a barcode →Build a daily picture.
Use the same food and serving selections to create a food diary. Create, read, update and delete entries in your app.
Connect an end user
With an API key, pass the January-End-User-ID header. Scoped client tokens carry their end-user identity. The demo previews selections without saving diary entries.
Make choices easier.
Compare calories and macros at the servings shown. Build comparisons directly from the nutrition fields in food JSON.
Find foods to compare →Bring the menu into your app.
Discover restaurants near a location and explore their menu items and nutrition. US & Canada coverage.
GET /v1.2/restaurantsGET /v1.2/restaurants/{restaurant_id}/menu-itemsRestaurant and menu API reference ↗Connect your product.
Keep your API key on the backend. For client apps, issue scoped, short-lived client tokens from your backend.
Read the integration guide ↗Get a developer key ↗