Portfolios, watchlists and live quotes inside Investing.com

Fusion Media Limited's app tracks live prices for more than 300,000 instruments across roughly 250 exchanges, in around 44 language editions, per its store listing and About page. Behind a login it holds a second layer that matters far more for integration: the holdings, watchlists and alerts a user builds on top of that feed. That private layer, plus the quote and economic-calendar surfaces the app reads, is what this page is about — how a third party reaches it under authorization, and what we hand over.

The bottom line: the data you most likely want is split between a user-private store and a licensed market feed, and each needs a different handling. For a live sync of a user's positions and alerts you'd run authorized protocol analysis of the logged-in session, because the built-in CSV download only gives a point-in-time snapshot and drops alerts entirely. We keep that export wired in as a cheap reconciliation check against what the session returns.

What the account holds, surface by surface

These rows reflect Investing.com's own naming for its portfolio types and tools. Granularity is what an integrator can realistically expect from each surface.

The authorized ways in

Three routes genuinely apply here. They differ in what they reach and how long they keep working.

Authorized protocol analysis of the app session

With the account holder's consent, we observe the JSON the app calls when its Portfolio, Alerts and instrument screens load, then rebuild those calls in clean source. This is the only route that reaches the per-user store — holdings, watchlists, alert rules — and it also covers live quotes for a defined symbol set. Effort is moderate; durability depends on the app's front end, which we account for with a re-validation step. Open-source projects such as investpy have long parsed Investing.com surfaces, which is independent evidence that these endpoints are stable enough to integrate against. Access to a consenting account is arranged with you during onboarding.

Native CSV export

The app lets an account holder download Holdings and Watchlist portfolios as CSV, with a Download Preferences dialog to pick columns, and it can import the same format from Yahoo or Google Finance. Low effort, very durable, and a good reconciliation baseline. It is a snapshot only: no alerts, no live prices, no event stream.

User-consented session access

If you are syncing on behalf of your own users, we run the same authenticated session the app uses, under each user's explicit consent and with their credentials never retained beyond the session. This reaches everything the user themselves can see. We set up the consent capture and the session handling as part of the build.

What lands in your repo at handoff

Everything below is tied to the surfaces above, not a generic package.

• An OpenAPI/Swagger specification covering the portfolio, alert, quote and calendar calls we mapped.
• A protocol and auth-flow report: how the app's session token and cookies are issued, refreshed and carried, written against what we observed.
• Runnable source for the key endpoints in Python and Node.js — holdings pull, watchlist read, alert mirror, quote and calendar fetch.
• Automated tests, including a fixture that diffs a live pull against a fresh CSV export so drift surfaces early.
• Interface documentation a developer can follow without us.
• Compliance and data-retention notes: what to store, what not to, and how the consent records map to GDPR and CCPA obligations.

Reading a portfolio, in practice

Illustrative shape of the holdings call. Exact paths and field names are confirmed during the build against the consenting account, not published here.

# Authorized protocol analysis of a logged-in Investing.com session.
# Host and paths shown are illustrative.

import httpx

session = httpx.Client(headers={
    "x-app-ver": app_version,            # version string the client sends
    "Cookie": consented_session_cookie,  # from a consenting account; not stored long-term
})

resp = session.get(
    "https://app-api.investing.example/portfolio/{pid}/holdings",
    params={"locale": "en", "currency": "USD"},
    timeout=15,
)
resp.raise_for_status()                  # 401 -> refresh token; 429 -> back off

for pos in resp.json()["data"]["positions"]:
    yield {
        "symbol":   pos["symbol"],
        "quantity": pos["amount"],
        "avg_cost": pos["avg_price"],
        "pl_pct":   pos["pl_perc"],       # normalized into your schema
    }

Error handling is half the work. A 401 means the session token expired and we refresh on the app's own flow; a 429 means we back off rather than hammer the endpoint. Both are wired into the delivered client.

Keeping the sync current

App front ends change. When Investing.com ships an update that moves a field or renames a path, a hard-coded client breaks quietly. We build a small contract test that runs on a schedule and flags a mismatch before it reaches your data. For the CSV path we pin the column layout, because the Download Preferences dialog lets the layout vary between accounts. Freshness is also a licensing question — see below.

Consent and data rights, as they actually apply

Investing.com is a financial-data and news platform, not a bank or broker, so this is not an open-banking or account-aggregation case. The governing frame is privacy law over the user-private store. Its EU editions fall under the GDPR; California users are covered by the CCPA, and the app publishes a dedicated California privacy form. Fusion Media names a Data Protection Officer (dpofficer@fusionmedialtd.com, per its privacy policy, last modified August 2025 per the published document). We work to that: access is authorized and logged, consent scope is recorded per user with an expiry and a revocation path, and we pull only the fields the integration needs. The market feed is governed separately by the exchange and vendor licences Fusion Media holds, which is why we treat real-time quote fields as redistribution-restricted by default. NDAs are in place where the work touches a client's user base.

Engineering details we plan around

Three things about this app shape the build, and we handle each rather than push them back to you.

• Web and mobile portfolios can drift. Users report that holdings and watchlists do not always stay in step between the website and the app. We map which surface is canonical for your users and read from that one, so a stale mirror does not look like a data loss.
• Real-time quotes are licensed, not free data. Because the 300k+ instrument feed comes from exchanges and vendors under Fusion Media's contracts, we separate exchange-licensed live values from delayed and reference data in the schema and label what is safe to store or re-serve. That keeps your downstream use inside the terms.
• Roughly 44 editions, different identifiers. Symbol IDs, currencies and calendar timezones shift across regional hosts like uk.investing.com. We pin the edition and locale up front so a position in one currency is not silently compared against a quote in another.

Pricing and how a build runs

The source you integrate against arrives as a working repository, not a slide deck. Source-code delivery starts at $300: you receive runnable code and docs for the Investing.com surfaces you named, and you pay only after handover, once you have checked it does the job. The other route is a hosted API you call per request, with no upfront fee — you pay for the calls you make and we run the maintenance. Either way a build takes one to two weeks. Tell us the app and which of its surfaces you need, and we scope it from there: start a project on the contact page.

What the app's screens show

Store screenshots of the surfaces above. Tap any image to enlarge.

Other apps in the same market-data category

If you are integrating Investing.com you are often unifying it with one or more of these. Each holds overlapping data a single interface layer can normalize.

• TradingView — charts, indicators and saved watchlists, with a social layer of shared ideas tied to symbols.
• Yahoo Finance — portfolios, watchlists and quote data, widely used as a CSV interchange source.
• Simply Wall St — fundamental analysis and portfolio scoring built on company financials.
• MarketWatch — market news, quotes and a virtual portfolio tied to the user's account.
• Stocktwits — symbol-tagged social sentiment and watchlists per user.
• Seeking Alpha — analysis, ratings and portfolio-linked alerts behind a login.
• Webull — a broker app holding real positions, orders and live quotes.
• Morningstar Investor — portfolio analytics, holdings X-ray and fund research data.

Sources and what was checked

Reviewed the app's store listing, its portfolio download and watchlist support articles, its published privacy policy, and the developer's About page to confirm the data surfaces, the CSV export behaviour and the data-protection contacts cited above; cross-checked surface reachability against a long-running open-source parser. Checked on 19 June 2026.

• Play Store listing (com.fusionmedia.investing)
• Investing.com support: downloading your portfolio (CSV)
• Investing.com privacy policy
• investpy — open-source parser of Investing.com surfaces

Mapping and notes by the OpenBanking Studio integration desk, June 2026.

Questions integrators ask about Investing.com

Can you sync a user's Investing.com Holdings and Watchlist into our own dashboard?

Yes. The Holdings and Watchlist portfolios live behind the account login, so we read them either through authorized protocol analysis of the logged-in session or through the app's own CSV download, then normalize positions, quantities, average price and the curated symbol lists into whatever schema your dashboard expects.

Is the real-time quote feed something we can redistribute?

Investing.com sources its 300,000-plus instrument quotes from exchanges and data vendors under Fusion Media's licences, so real-time fields carry redistribution terms. We separate exchange-licensed live values from delayed and reference data in the integration and document which fields are safe to store or re-serve, so your use stays inside the licence.

Which Investing.com edition do you build against, the global site or a regional one?

We pin the edition during the build. Investing.com runs in roughly 44 language editions with regional hosts such as uk.investing.com, and symbol identifiers, currencies and economic-calendar timezones shift between them. We fix the edition and locale to the one your users actually use so the data lines up.

We already export portfolio CSVs by hand, what does an integration add?

The CSV download is a point-in-time snapshot of Holdings or a Watchlist and carries no alerts or live prices. An integration turns that into a repeatable call: scheduled position pulls, alert rules and quote refreshes on your timing, returned as JSON your systems can act on without a person clicking download.