Choose the Best Free Financial News API
Find a free financial news API that matches your sources, filters, freshness, usage rights, and production limits—then test it before you build.
TL;DR
A usable free tier, relevant financial sources, predictable JSON, practical filters, and terms that allow the intended project.
Free may mean no key, a trial, or a recurring quota. Check request limits, delay, history, attribution, and commercial-use rules.
Run the same company, topic, language, and date queries against candidates; inspect relevance, duplicates, timestamps, and missing fields.
QVeris helps agents discover and call external capabilities; each provider’s current data rights and limits still apply.
Define the free financial news API requirements first
A useful shortlist starts with the product decision, not the provider name. A portfolio alert needs precise company and event matching; a macro dashboard needs central-bank, statistics-agency, and policy coverage; a multilingual research system needs language metadata and regional publishers. The same API can be excellent for one of these jobs and unsuitable for another.
Coverage and relevance
Decide whether you need broad corporate headlines, company-specific news, financial markets, industries, economic policy, or a regional feed. A general news category may not support ticker-level monitoring.
Freshness, history, and full text
Record timestamp semantics, update cadence, archive window, pagination rules, and whether the API returns metadata, a summary, or licensed article text. Test “real-time” rather than assuming it.
Keep at least three times when possible: the publisher's original publication time, the provider's ingestion time, and your application's retrieval time. If an article is corrected or republished, preserve the update time separately. Without those distinctions, a feed may look fast while actually surfacing old stories with new ingestion timestamps.
Free tier and usage rights
Check calls per minute and month, allowed environments, caching, attribution, redistribution, commercial use, and upgrade behavior. The free plan must fit both your test volume and legal use case.
Distinguish the right to call an API from the right to display or redistribute its content. A plan may permit server-side analysis while limiting headline display, long-term storage, images, article text, or customer-facing redistribution. Record the permitted output for each use case before the integration becomes part of a product.
How to compare free financial news API options
| Criterion | Verify | Why it matters |
|---|---|---|
| Sources | Publishers, countries, languages, categories | Relevance and geographic blind spots |
| Filters | Company, ticker, topic, source, language, date | Less noisy post-processing |
| Response | Stable IDs, URLs, timestamps, summaries, images | Deduplication and display |
| Free limits | Quota, throttling, delay, history, CORS, key | Demo versus sustainable integration |
| Rights | Attribution, caching, commercial use, redistribution | Technically and legally usable |
| Quality | Duplicate rate, entity precision, corrections, missing fields | Determines how much cleanup the product must own |
| Operations | 429 behavior, pagination stability, retries, status visibility | Prevents silent gaps and duplicate alerts |
Best free financial news API options compared
“Free” below means a documented free plan, open endpoint, or no-cost evaluation path observed during research. Plans change, so verify the linked official documentation before building.
| API | Best fit | Notable capability | Free-plan caution |
|---|---|---|---|
| Finnhub | Company-specific stock news | Ticker news and real-time updates | Free license is listed for personal use; sentiment is premium. |
| Marketaux | Finance-first feeds | Entity, symbol, exchange and language filters | Daily request allowance depends on the current plan. |
| Alpha Vantage | News plus sentiment experiments | Ticker/topic filters and sentiment fields | Confirm endpoint availability and current call limits. |
| Financial Modeling Prep | Stock news alongside financial data | Latest stock, forex, and crypto news endpoints | Check which stable endpoints remain in the free plan. |
| GDELT | Open global event and media research | Large multilingual event/news datasets | Requires more normalization than a finance-specific feed. |
| NewsAPI | General-news prototypes | Source, keyword, language and date search | Developer plan restrictions may exclude production use. |
| The Guardian Open Platform | One authoritative publisher archive | Searchable section and tag metadata | Not a broad multi-source financial feed. |
For many developers, Finnhub or Marketaux is the most direct starting point; Alpha Vantage is useful when sentiment is central. This is a fit assessment, not a universal ranking.
Choose a financial news API by the job it must perform
Do not average every feature into one score. First reject candidates that fail a non-negotiable requirement—such as production rights, language coverage, company filters, or a usable update delay—then compare quality and cost among the remaining options.
Prioritize ticker or entity filters, precise relevance, correction handling, and low end-to-end delay. Test subsidiaries, ambiguous company names, mergers, and articles that mention several issuers.
Prioritize central-bank, government, policy, and regional coverage plus a useful archive. GDELT can broaden event discovery, but expect more entity cleanup and relevance scoring.
Verify whether sentiment is article-level, entity-level, or ticker-level; whether the model and labels are documented; and whether the field is included in the free plan. Never treat an undocumented score as a trading signal.
Licensing, attribution, images, canonical links, deletion requests, and display rights become first-class requirements. A technically convenient developer tier may still be unsuitable for a public product.
Integrate a free financial news API step by step
Include a large company, a smaller company, an industry topic, two languages, a date boundary, and an intentionally empty query.
Store credentials server-side, set a timeout, and log the status code, response time, rate-limit headers, and raw response during evaluation.
Map provider fields into your article model. Prefer stable IDs; otherwise combine canonical URL, normalized title, source, and publication time.
Handle 429, malformed items, missing timestamps, empty pages, and outages. Cache only where provider terms allow it.
For every test query, label whether each article is truly about the company or event, merely mentions it, or is unrelated. Then measure source publication delay and API availability delay independently. A fast feed full of weak mentions can be worse for alerts than a slightly slower feed with precise entity and event matching.
Convert daily and per-minute limits into the number of symbols, topics, refresh cycles, and pagination requests your workflow actually needs. Include retries, empty polling windows, enrichment calls, and traffic bursts. Record the first point at which the free plan forces stale results, incomplete coverage, or an unsupported production license.
Save the test date, plan name, documentation links, raw sample, duplicate rate, relevant-result rate, p50 and p95 latency, missing-field rate, language coverage, and licensing conclusion. Re-run the same corpus periodically because sources, quotas, response schemas, and free-tier terms change after the initial integration.
Worked example: normalize one article before deduplication
Suppose one provider returns published_at, another returns datetime, and a third exposes only a source URL and title. Map them into a common record with provider_id, canonical_url, source, published_at, ingested_at, symbols, language, and headline. Normalize tracking parameters and publisher aliases, but keep the raw payload for audit.
Deduplicate in layers: use a stable provider ID first, then canonical URL, then a conservative fingerprint of normalized source, title, and publication window. Do not merge articles merely because their headlines are similar; wire stories may be republished by several outlets, while genuine updates can reuse most of an earlier headline. Store the merge reason so a reviewer can reverse a bad match.
Use QVeris to discover financial news capabilities
QVeris can help an AI agent discover, inspect, and call relevant external capabilities instead of hard-coding every provider path. It does not change a provider’s coverage, licensing, quota, or freshness.
- Explore the QVeris tool details for news and financial data capabilities.
- Inspect the capability definition and inputs before an agent calls it.
- Keep provider limits, attribution, and validation in application policy.
Frequently asked questions
What is the best free financial news API?
There is no universal winner. Finnhub is strong for company news, Marketaux for finance-focused filters and entity analysis, Alpha Vantage for news plus sentiment, and GDELT for open global event research. Verify current limits and rights.
Is there a free API for stock news?
Yes. Several providers offer free tiers or trials for company or market news, but quotas, delays, history, attribution, and commercial-use rules differ.
Which financial news API includes sentiment?
Alpha Vantage and Marketaux document sentiment or entity analysis features. Check whether those fields are included in the current free plan and how scores are defined.
Can I use a free financial news API in production?
Only if the provider's current plan and license permit it. Many free plans are intended for evaluation, have low quotas, or restrict redistribution.
How do I choose a financial news API?
Test the same ticker and date window across candidates, then compare freshness, coverage, fields, duplicates, rate limits, history, licensing, and failure behavior.
Do free news APIs provide full article text?
Often they return metadata, headlines, summaries, and source URLs rather than licensed full text. Verify the response schema and content rights.