Tuesday, August 18, 2026
Request Any Source: finlight Custom Feeds
Request Any Source: finlight Custom Feeds
Most news APIs give you a fixed catalog: you get the sources they decided to cover, and if the one your strategy depends on is missing, that is the end of the conversation. finlight works differently. If we do not cover a source yet, you can ask us to build it. Custom feeds turn "we don't have that" into "tell us, and we will." See the full offering at finlight.me/custom-feeds.
What a custom feed is
You name a source. We build it, maintain it, and stream it to you through the same integration you already use, fully normalized and entity-tagged so it lands in the same shape as every other finlight article. You do not get a raw scrape to clean up yourself; you get a production feed that fits the rest of your pipeline.
That covers the kinds of sources teams keep asking for:
- Regulatory filings — SEC, ESMA, BaFin, and other supervisors.
- Government and central-bank publications — policy statements, releases, and notices.
- Exchange and company announcements — the primary disclosures, at the source.
- Commodity and shipping notices — niche operational feeds that move specific markets.
- Earnings releases — straight from the issuer.
If it publishes financial information on a schedule, it is a candidate.
How it works
The process is three steps, and you stay inside the integration you already built:
- Request a source. Tell us what you need and how you would use it. We typically reply within two business days.
- We build and maintain it. We handle extraction, normalization, and entity tagging, and we keep it working when the source changes its format. Maintenance is part of the deal, not an afterthought.
- Consume it. The feed arrives through your existing REST, WebSocket, or webhook integration, in the same enriched shape as the rest of your articles. For how those delivery methods compare, see What the finlight API Can Do.
Because the output matches the standard article shape, the same filters, sentiment, and company entities you already rely on apply to your custom source too.
What it costs
Custom feeds use a per-source subscription, not per-request pricing. The price depends on the source's complexity and how often it updates, which is why it is a short conversation rather than a fixed line on a pricing page. You tell us the source and a rough budget, and we scope it from there. The live request form and budget ranges are on finlight.me/custom-feeds.
This sits alongside, not inside, your regular plan. If you are still deciding which standard tier fits your core workload, the plan guide walks through that, and custom feeds layer on top once you know the source you need.
When to ask for one
A custom feed is the right move when:
- Your edge depends on a source no general news API carries.
- You need a primary disclosure (a filing, an exchange notice) at the source, not a secondary report.
- You have been maintaining a fragile in-house scraper and would rather own the signal than the plumbing.
If that sounds like your situation, the source you have been working around can become a maintained, normalized feed instead.
Next steps
- Request a source at finlight.me/custom-feeds.
- New to finlight? Start with the free plan to see the standard catalog first.
- Questions about a specific source? Email info@finlight.me or ask in Discord.