Skip to content
What's on the menu? logo

Is What's on the menu? API down?

Current status, daily uptime history and troubleshooting for the What's on the menu? API (Food & Drink).

No, What's on the menu? is up

What's on the menu? answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1143 ms with HTTP 200.

Checking What's on the menu? now…

Sending a request from our server.

What's on the menu? API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
1143 ms · HTTP 200
Last up
Now

We check What's on the menu?'s listed URL (http://nypl.github.io/menus-api/) once a day. History started when What's on the menu? was first checked, so new entries show fewer than 30 days.

What's on the menu? API not working for you?

  1. What's on the menu? needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
  2. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  3. If calls fail only in the browser with a CORS error, What's on the menu? may not allow cross-origin requests. Call it from your server instead.
  4. What's on the menu? is listed without HTTPS. Browsers block plain-HTTP requests from HTTPS pages (mixed content).
  5. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  6. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Food & Drink APIs up at their last check

  1. 1BaconMockup logo

    BaconMockup API

    Online · 908 ms

    Resizable bacon placeholder images. A free food & drink API by baconmockup.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2Daily Food Recalls logo

    Daily Food Recalls API

    Online · 780 ms

    U.S. FDA and USDA food recalls, merged and normalized, updated daily.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3ExactCup logo

    ExactCup API

    Online · 576 ms

    Cooking ingredient densities: grams per US cup, tablespoon, teaspoon and mL.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4FiberUp Fiber Database logo

    Dietary fiber per serving and per 100 g, split into soluble and insoluble, for ~200 common foods.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5Foodish logo

    Foodish API

    Online · 676 ms

    Random pictures of food dishes.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all What's on the menu? alternatives · APIs down right now

What's on the menu? API status FAQ

Is What's on the menu? API down right now?

What's on the menu? answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1143 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether What's on the menu? is responding at this moment.

How do you check whether What's on the menu? API is up?

Once a day our checker requests What's on the menu?'s listed URL (http://nypl.github.io/menus-api/) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

What can I use if What's on the menu? API is down?

Free Food & Drink APIs that were up at their last check include BaconMockup, Daily Food Recalls, ExactCup. See the full list of What's on the menu? alternatives for a comparison.

Why does What's on the menu? API work for others but not for me?

What's on the menu? needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, What's on the menu? may not allow cross-origin requests. Call it from your server instead.