Is Noms API down?
Current status, daily uptime history and troubleshooting for the Noms API (Food & Drink).
Possibly: Noms's last check failed
Our latest daily check of Noms (Oct 24, 2026, 12:25 UTC) failed: it answered HTTP 503. One failure can be a blip; the live check below tells you whether it's still failing.
Checking Noms now…
Sending a request from our server.
Noms API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- It answered HTTP 503
- Last up
- Not seen up yet
We check Noms's listed URL (https://noms.sh/docs) once a day. History started when Noms was first checked, so new entries show fewer than 30 days.
What does HTTP 503 mean? Read the 503 explainer.
Noms API not working for you?
- Noms 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 it works from one network but not another, check firewalls, VPNs and regional blocks.
- 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
BaconMockup API
Online · 908 msResizable bacon placeholder images. A free food & drink API by baconmockup.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Daily Food Recalls API
Online · 780 msU.S. FDA and USDA food recalls, merged and normalized, updated daily.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
ExactCup API
Online · 576 msCooking ingredient densities: grams per US cup, tablespoon, teaspoon and mL.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
FiberUp Fiber Database API
Online · 898 msDietary 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
Foodish API
Online · 676 msRandom pictures of food dishes.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Noms API status FAQ
Is Noms API down right now?
Our latest daily check of Noms (Oct 24, 2026, 12:25 UTC) failed: it answered HTTP 503. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether Noms is responding at this moment.
How do you check whether Noms API is up?
Once a day our checker requests Noms's listed URL (https://noms.sh/docs) 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 Noms 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 Noms alternatives for a comparison.
Why does Noms API work for others but not for me?
Noms 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 it works from one network but not another, check firewalls, VPNs and regional blocks.