Is Barcode Lookup API down?
Current status, daily uptime history and troubleshooting for the Barcode Lookup API (Shopping).
No, Barcode Lookup is up
Barcode Lookup answered our last daily check (Nov 15, 2026, 13:58 UTC) in 806 ms with HTTP 200.
Checking Barcode Lookup now…
Sending a request from our server.
Barcode Lookup API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 806 ms · HTTP 200
- Last up
- Now
We check Barcode Lookup's listed URL (https://dataandapis.com/apis/barcode-lookup) once a day. History started when Barcode Lookup was first checked, so new entries show fewer than 30 days.
Barcode Lookup API not working for you?
- Barcode Lookup 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.
- Barcode Lookup doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.
- 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.
Shopping APIs up at their last check
- 1
BirkinBagStock API
Online · 776 msIndependent Hermès resale index: inventory, market prices, auction calendar and results.
- No API key needed
- 100% uptime (30 days)
- Returns JSON at its URL
- Callable from the browser (CORS)
No authHTTPSCORS - 2
ARC API
Online · 743 msOpen data on whether AI shopping agents can reach checkout at specific online stores.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Marketplace Fee Data API
Online · 2056 msSeller fee schedules for 21 e-commerce marketplaces and payment processors as JSON.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
Nuvinty API
Online · 1967 msUK luxury list prices, price history, increases and partner pre-owned asking prices.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
OneFindMe API
Online · 2119 msSearch AliExpress in any language: price, rating and orders for the delivery country.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all Barcode Lookup alternatives · APIs down right now
Barcode Lookup API status FAQ
Is Barcode Lookup API down right now?
Barcode Lookup answered our last daily check (Nov 15, 2026, 13:58 UTC) in 806 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Barcode Lookup is responding at this moment.
How do you check whether Barcode Lookup API is up?
Once a day our checker requests Barcode Lookup's listed URL (https://dataandapis.com/apis/barcode-lookup) 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.
How reliable is Barcode Lookup API?
Barcode Lookup answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.
What can I use if Barcode Lookup API is down?
Free Shopping APIs that were up at their last check include BirkinBagStock, ARC, Marketplace Fee Data. See the full list of Barcode Lookup alternatives for a comparison.
Why does Barcode Lookup API work for others but not for me?
Barcode Lookup 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. Barcode Lookup doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.