Is New York Times API down?
Current status, daily uptime history and troubleshooting for the New York Times API (News).
No, New York Times is up
New York Times answered our last daily check (Oct 24, 2026, 12:25 UTC) in 854 ms with HTTP 200.
Checking New York Times now…
Sending a request from our server.
New York Times API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 854 ms · HTTP 200
- Last up
- Now
We check New York Times's listed URL (https://developer.nytimes.com/) once a day. History started when New York Times was first checked, so new entries show fewer than 30 days.
New York Times API not working for you?
- New York Times 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, New York Times may not allow cross-origin requests. 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.
News APIs up at their last check
- 1

Florida Man API
Online · 1018 msStatic JSON dataset of 10,000+ Florida Man headlines by date.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2

Noozra API
Online · 852 msFree news headlines from 200+ curated RSS sources.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Spaceflight News API
Online · 493 msThe Spaceflight News API lets you add space related news to your apps.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4

Inshorts News API
Online · 981 msUnofficial API of Inshorts written in Flask.
- No API key needed
- HTTPS
No authHTTPSCORS ? - 5
Currents API
Online · 1072 msReal-time and historical global news with multilingual support.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS
Compare all New York Times alternatives · APIs down right now
New York Times API status FAQ
Is New York Times API down right now?
New York Times answered our last daily check (Oct 24, 2026, 12:25 UTC) in 854 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether New York Times is responding at this moment.
How do you check whether New York Times API is up?
Once a day our checker requests New York Times's listed URL (https://developer.nytimes.com/) 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 New York Times API is down?
Free News APIs that were up at their last check include Florida Man, Noozra, Spaceflight News. See the full list of New York Times alternatives for a comparison.
Why does New York Times API work for others but not for me?
New York Times 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, New York Times may not allow cross-origin requests. Call it from your server instead.