Introducing “Fetch Article by Link” — On-Demand News Enrichment via REST API

We’re excited to announce a new addition to the finlight REST API that gives you even more flexibility when working with news data:

Fetch Article by Link

This new endpoint allows you to retrieve a fully structured and enriched article using only its original URL — whenever you need it.

---

Why We Built This

Many teams using finlight process news in multiple stages.

A common workflow looks like this:

• Ingest news in real time (often raw and lightweight)
• Store article links or partial data
• Run internal analysis, signals, or filtering
• Enrich only selected articles later

Until now, this required storing full payloads upfront or maintaining additional mappings.

With Fetch Article by Link, you can now:

Ingest fast, decide later, enrich only what matters.

---

What Does “Fetch Article by Link” Do?

The new REST endpoint lets you request a complete finlight article by providing its original source URL.

finlight will automatically:

• Identify the article
• Retrieve the full structured content
• Apply enrichment such as sentiment and entity tagging
• Return the complete article object

This enables seamless transitions from raw ingestion to deep analysis, without changing your architecture.

---

Ideal Use Cases

This feature is especially useful if you:

• 📰 Consume raw WebSocket news first
• 📊 Perform delayed or selective enrichment
• 🧪 Re-analyze historical articles
• 🔍 Validate or enrich articles from external systems
• 📈 Associate news with tickers, signals, or models after ingestion

For example:

• Stream raw news for speed
• Store article URLs
• Fetch enriched data only for articles that trigger interest

Efficient, modular, and cost-conscious.

---

Works Perfectly with Raw & Enriched Pipelines

The Fetch Article by Link endpoint integrates naturally with existing finlight workflows:

• Combine with the WebSocket Raw Channel for ultra-low latency
• Use REST enrichment only when required
• Avoid unnecessary upfront processing
• Maintain full control over your data lifecycle

It’s designed for teams building scalable, developer-first news systems.

---

How It Works

Using the endpoint is straightforward.
All you need is the original article link — finlight handles the rest.

Example: Fetch Article by Link

Below is an example showing how to retrieve a fully enriched article using its original source URL.

curl -X POST "https://api.finlight.me/v2/articles/by-link" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "link": "https://www.reuters.com/technology/nvidia-results-ai-demand-2024-02-21/"
  }'

Example response:

{
  "status": "ok",
  "article": {
    "link": "https://somepage.com/article/milan-cortina-olympics-bam-park-installation-art-7d651b0eac41204f57a5f3d8bd023455",
    "source": "www.reuters.com",
    "title": "Olympic Milan park invites the public spirit",
    "summary": "A new summary",
    "publishDate": "2026-02-08T18:17:40.000Z",
    "language": "en",
    "sentiment": "neutral",
    "confidence": "0.9999229907989502",
    "images": [],
    "content": "...",
    "companies": []
  }
}

For full parameter details and response fields, see the documentation:
https://docs.finlight.me/v2/rest-endpoints/#fetch-article-by-link

---

Designed for Flexibility and Control

With this feature, you gain:

• 🔗 Direct enrichment via article URL
• 🧠 Full sentiment and entity analysis on demand
• 🛠️ Simple REST-based integration
• 🔄 The ability to re-fetch and reprocess articles anytime

You decide when an article becomes important enough for deeper insight.

---

Available Now

The Fetch Article by Link endpoint is live and available today in the finlight REST API.

If you already work with article URLs — or want more control over when enrichment happens — this feature was built for you.

As always, we’re excited to see what you build with finlight.