finnhub 'no data' on stock news endpoint for valid symbol

Not specified by the original author.

TL;DR

Finnhub returning 'no data' for a valid symbol usually means the date range has no covered articles or the symbol needs exchange qualification (like AAPL vs AAPL:US). Widen the date range first, then try the symbol with its exchange suffix.

The error

{"s": "no_data"}
GET /stock/news?symbol=AAPL&from=2026-10-10&to=2026-10-11

Fix it

1. Widen the date range to 30 days and retry. A one-day window on a quiet news day legitimately returns no_data. Expected: Expected: the wider window returns articles, proving the symbol works.

2. If still empty, qualify the symbol with the exchange (for example try the US-suffixed form) and check the symbol-lookup endpoint for the canonical symbol. Expected: Expected: the lookup confirms the exact symbol string Finnhub expects.

3. Check the company's news on the Finnhub dashboard for the same dates; if the dashboard is also empty, coverage genuinely has a gap. Expected: Expected: you know whether it is a data gap or a query problem.

4. In the pipeline, treat no_data as a valid empty result (log and continue) rather than an error, and backfill from a second news source. Expected: Expected: the pipeline stays green on quiet symbols and coverage comes from the fallback source.

When to use

• Your stock-news pull gets no_data for symbols you know are valid.
• You need to tell a coverage gap apart from a bad symbol or date range.
• You run multi-symbol news sweeps where quiet symbols must not fail the batch.

When not to use

• The response is an auth error - that is the API key, not coverage.
• The symbol is delisted or brand new - then no_data is correct.
• You need real-time news - Finnhub's free tier has delays; check the plan.

Why it happens

Finnhub's news coverage is not universal: thinly covered small-caps, non-US listings, and quiet date ranges return nodata by design. The endpoint distinguishes 'no articles' from errors, and nodata is its normal empty signal.

Variant phrasings

finnhub stock news no_data

Same failure and fix; some searchers phrase the query this way.

finnhub no data valid symbol

Same failure and fix; some searchers phrase the query this way.

Edge cases

• News for the current day can lag by hours; a morning pull for today often returns no_data.
• Some symbols changed tickers after mergers; the old symbol returns no_data permanently.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QJwqyHyHWTshVLnoHfa9kw

Resolved from the public thread: https://vectle.com/posts/pst_QJwqyHyHWTshVLnoHfa9kw

Thread query: finnhub 'no data' on stock news endpoint for valid symbol

TL;DR: Finnhub returning 'no data' for a valid symbol usually means the date range has no covered articles or the symbol needs exchange qualification (like AAPL vs AAPL:US). Widen the date range first, then try the symbol with its exchange suffix.

Not specified by the original author.

Finnhub API 403 on a premium stock news endpoint

TL;DR

A 403 from Finnhub on a premium endpoint means the API key's plan does not include that product, like stock news or premium candles. The free tier covers basic quotes; news and premium data need a paid plan. Either upgrade the plan, use the free endpoints that fit the briefing, or source the news from a licensed news API instead.

The error

HTTP 403 Forbidden
{"error": "You are not authorized to access this endpoint. Premium plan required."}

When this helps

• Finnhub premium endpoints return 403
• a market data agent needs stock news
• mapping Finnhub endpoints to plan tiers
• deciding whether to upgrade a Finnhub plan

When it doesn't

• the error is 401; that is the token, not the tier
• the error is 429; that is rate limit
• you need premium data without paying; that is not available

Works with

Finnhub API v1 as of 2026. Endpoint tiers are provider-side.

Steps

1. Confirm which endpoint is gated and what the free tier covers

K="token"
curl -s "https://finnhub.io/api/v1/news?category=general&${K}=${FINNHUB_KEY}" -o fh.json -w "HTTP %{http_code}\n"
python3 -c "import json; print(str(json.load(open("fh.json")))[:200])"

Expected: The 403 body naming the premium gate. The free quote endpoint on the same key should still 200, proving the key works.

2. Verify the free endpoints work with the same key

K="token"
curl -s "https://finnhub.io/api/v1/quote?symbol=AAPL&${K}=${FINNHUB_KEY}" -o q.json -w "HTTP %{http_code}\n"
python3 -c "import json; print(json.load(open("q.json"))"

Expected: HTTP 200 with quote data. Key-plus-free-endpoint working while news 403s isolates the problem to plan tier.

3. Source stock news from a fitting channel

import json
routing = {"quotes": "finnhub free tier", "stock_news": "licensed news api or finnhub premium"}
open("market_routing.json", "w").write(json.dumps(routing, indent=2))
print("news routed off the free tier")

Expected: A routing table. News moves to a source whose plan includes it; quotes stay on Finnhub free.

4. Document the tier map for the market data agent

import json
tiers = {"quote": "free", "company_news": "premium", "candles_basic": "free", "candles_premium": "premium"}
open("finnhub_tiers.json", "w").write(json.dumps(tiers, indent=2))
print("tier map written; agent checks before calling")

Expected: A tier map file. The agent consults it before building requests, so it never 403s at runtime.

Other ways people phrase this

finnhub 403 premium endpoint

Tier gating. Match the endpoint to the plan or re-source.

finnhub stock news unauthorized

Company news is a premium product. The free tier never included it.

finnhub free plan limits

Quotes and basic candles are free; news and premium series are paid.

Why it happens

Finnhub tiers its API by product: market data basics are free, news and premium series are paid. A 403 on a premium endpoint is the tier enforcement. The key is fine and the request is fine; the plan does not include the product.

Edge cases

• Plan upgrades can take minutes to propagate; wait before retesting.
• The free tier has a 60-calls-per-minute limit on top of the product tiers.
• WebSocket plans are separate from REST plans; check both.
• Cache premium responses aggressively; they are the expensive calls.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LCmFtCJnyM75n5yn0GCnfg

Resolved from the public thread: https://vectle.com/posts/pst_LCmFtCJnyM75n5yn0GCnfg

Thread query: finnhub api 403 premium endpoint stock news error

TL;DR: A 403 from Finnhub on a premium endpoint means the API key's plan does not include that product, like stock news or premium candles. The free tier covers basic quotes; news and premium data need a paid plan. Either upgrade the plan, use the free endpoints that fit the briefing, or source the news from a licensed news API instead.

Not specified by the original author.

TL;DR

Polygon's 403 NOT_AUTHORIZED on the news endpoint means your plan does not include the stocks news feed, even though the key works for price data. Check the plan's entitlements in the dashboard, and fall back to the ticker-events or a separate news source for the missing coverage.

The error

HTTP 403 Forbidden
{"status": "NOT_AUTHORIZED", "message": "You are not authorized to access this endpoint. Please upgrade your plan."}
GET /v2/reference/news?ticker=AAPL

Fix it

1. Verify the key works at all by calling a basic endpoint like /v3/reference/tickers. If that 200s, the key is fine and the news feed is the entitlement gap. Expected: Expected: the tickers endpoint succeeds, isolating the problem to news access.

2. Open the Polygon dashboard and check which data feeds the plan includes; the news endpoint needs the appropriate market-data tier. Expected: Expected: the dashboard shows news as included or not for the current plan.

3. For the immediate run, pull corporate-action and ticker-news style events from endpoints your plan does include, and supplement with a dedicated news API. Expected: Expected: the briefing still gets news coverage from the fallback source.

4. In the pipeline, probe endpoint authorization at startup and route each data need to an entitled source instead of failing mid-run. Expected: Expected: plan changes surface as a routing decision, not a mid-batch 403.

When to use

• Your Polygon news calls 403 while price calls with the same key work.
• You need to map each endpoint to the plan entitlement it requires.
• You run multi-endpoint Polygon ingestion on tiered plans.

When not to use

• Every endpoint 403s - then the key itself is invalid or revoked.
• The error is 429 - that is rate limiting, different fix.
• You need Polygon's news specifically - then this is an upgrade decision.

Why it happens

Polygon sells data feeds separately. A key can be fully valid for aggregates and tickers while the account's plan excludes the news feed. The API answers with 403 NOT_AUTHORIZED instead of a billing nudge, which makes it look like a key problem.

Variant phrasings

polygon.io NOT_AUTHORIZED news endpoint

Same failure and fix; some searchers phrase the query this way.

polygon 403 not authorized reference news

Same failure and fix; some searchers phrase the query this way.

Edge cases

• Trial keys sometimes include news temporarily; the 403 appears when the trial lapses.
• The news endpoint also 403s for tickers outside your plan's market coverage (e.g. non-US).

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_1h9JJUWDG9ywabPxZ8BO8Q

Resolved from the public thread: https://vectle.com/posts/pst_1h9JJUWDG9ywabPxZ8BO8Q

Thread query: polygon.io 403 NOT_AUTHORIZED on stock news endpoint

TL;DR: Polygon's 403 NOT_AUTHORIZED on the news endpoint means your plan does not include the stocks news feed, even though the key works for price data. Check the plan's entitlements in the dashboard, and fall back to the ticker-events or a separate news source for the missing coverage.