Getting at the trading records behind a markets.com login

Behind a markets.com login sit open positions, a closed-trade history, pending orders and downloadable account statements — the same records the app surfaces under Account → Reports. The app advertises trading volume in the trillions and a multi-million user base on its store listing; what matters for an integration is narrower and concrete: per-account exposure, realized P&L and cash movements, all bound to one authenticated session. This brief sets out where those records live, the authorized way to read them on behalf of the account holder, and what we hand back.

For an account already running on MT4 or MT5, the steadiest read is the MetaTrader server protocol — it survives front-end redesigns and returns structured trades directly. Where a client only uses the native web and mobile platform, we pair a consented capture of the My Portal session for live positions with scheduled parsing of the statement PDF for the reconciled ledger. Which combination we propose depends on what account types you actually hold; we settle that early.

What the account actually holds

Each row below maps to a surface a markets.com user can already see, named the way the app names it.

Reaching the data

Three authorized routes apply here. We arrange the access each one needs together with you during onboarding — a consenting account, or your own login, or MetaTrader credentials — so none of this is something you have to assemble before we start.

Consented protocol analysis of the platform session

We observe and reimplement the authenticated My Portal traffic the web and mobile platform use — the calls behind the Report Center, the closed-positions report and the live positions feed. Reachable: everything the signed-in user can see. Effort is moderate; durability is tied to the front end, so we add a re-validation pass that flags when a request shape shifts. Run against a consenting account.

MetaTrader server protocol for MT4/MT5 accounts

markets.com lets a client open MetaTrader account types — the help centre walks through adding an "MT4 - CFD" or MT5 account and logging in with an account number, password and server. Against that server we read account info, open trades and history through the platform's data interface. This is the most stable surface: balances, equity, open and closed trades and order history arrive structured, and the protocol does not move when a web page is restyled.

Native statement export

The Report Center generates an account statement you can open in a new window or download as a PDF. We automate that retrieval and parse it into structured rows. It is the lowest-effort, most durable surface, though coarser than the live feeds — it is period-level ledger data, not tick-by-tick.

What lands in your repo

Everything is tied to the surfaces above, not a generic template:

• An OpenAPI description of the normalized endpoints — positions, closed-trades, orders, statement, cash-movements.
• A protocol and auth-flow report: how the My Portal session token is obtained and refreshed, and the MetaTrader login handshake for MT4/MT5 accounts.
• Runnable source for the key reads in Python and Node.js, including the statement-PDF parser.
• Automated tests against recorded fixtures so a portal change surfaces as a red test, not a silent gap.
• Interface documentation and data-retention guidance scoped to the operating entity.

A sample pull

Illustrative shape of the consented statement read, confirmed against the live surfaces during a build — fields and the session step are reconstructed, not guessed.

# Authorized read of a markets.com account statement (illustrative)
session = portal_login(user, secret)        # My Portal session cookie/token

stmt = session.get(
    "/report-center/account-statement",
    params={"from": "2026-01-01", "to": "2026-03-31", "format": "json"},
)

# normalized rows joined with the closed-positions report
for row in stmt["entries"]:
    yield {
        "value_date": row["date"],
        "type": row["type"],            # DEPOSIT | WITHDRAWAL | TRADE | FEE
        "instrument": row.get("symbol"),
        "amount": row["amount"],
        "balance_after": row["balance"],
    }

# MT4/MT5 accounts read the same fields via the MetaTrader server protocol,
# keyed on (login, server); we reconcile both into one schema.

Error handling matters more than the happy path: an expired session returns a redirect to login rather than a clean 401, so the client treats an unexpected HTML body as a re-auth trigger.

Consent, regulation and how we handle records

A CFD trading account is not a payment account, so open-banking Account Information Services rules do not reach it — there is no AIS consent flow to ride here, and we do not pretend one exists. The dependable basis is the account holder's own authorized access. For accounts under Safecap Investments, the EU regulator is CySEC and the relevant data right is GDPR access and portability over the records the operator holds; South-African accounts fall under FSCA and POPIA, and the SVG entity under its own registration. We work from authorized or user-consented access only, keep a consent record and an access log, minimize what we pull to the agreed domains, and sign an NDA where the engagement calls for one. No authentication is ever defeated; the work is interface reconstruction for interoperability on behalf of the account owner.

Build notes worth stating up front

Two things about this app shape the build, and we account for both:

• The platform offers both "MT4 - CFD" and MT5 account types alongside the native platform, and a single login can carry several sub-accounts in different base currencies and leverage. We map each account type's fields and normalize them so a multi-sub-account client reconciles into one feed rather than three mismatched ones.
• The Report Center statement is session-bound and rendered server-side, so we design the pull around the My Portal session lifetime and re-validate when the portal front end changes — rather than assuming a fixed scrape that quietly breaks.
• Because the same brand operates through Safecap (Cyprus), Markets South Africa and Markets International (SVG), a login can resolve to a different operating entity with a different statement format. We confirm the entity during onboarding and scope the parser to it so figures reconcile.

Where this gets used

• A multi-strategy desk syncs open positions and used margin from several MT5 sub-accounts into a single risk dashboard every minute.
• An accountant ingests quarterly statement PDFs automatically and reconciles deposits and withdrawals against the funding bank.
• A reporting tool pulls the closed-positions history nightly to compute realized P&L for tax filing in the account's jurisdiction.

What the app's surfaces look like

Store screenshots of the surfaces the integration reads — click to enlarge.

Comparable apps in the same space

Other CFD and forex apps a unified integration tends to sit alongside. Listed for ecosystem context only.

• CMC Markets — proprietary platform holding positions, orders and account history across thousands of CFD instruments.
• IG — broad multi-market accounts with order and statement records behind a single login.
• eToro — social and copy-trading account state, including copied-portfolio positions.
• Pepperstone — MT4/cTrader accounts whose trade history reads through the MetaTrader server protocol.
• Capital.com — CFD account with positions, orders and cash movements in its own portal.
• AvaTrade (AvaTradeGO) — multi-asset CFD accounts with automated-trading hooks and standard statement exports.
• City Index — forex, indices and commodities accounts with downloadable activity reports.
• BlackBull Markets — ECN accounts reachable through MetaTrader-style logins.
• OANDA — forex and CFD accounts with a well-defined transaction and position model.
• Vantage — MT4/MT5 accounts whose balances and trades sit on the MetaTrader server.

Sources and how this was checked

Checked in June 2026 against the markets.com help centre and company pages, alongside the Google Play listing for com.markets.android. Specifics on report access and MetaTrader account creation come from the help articles below; the regulatory entities are drawn from the company's own group page and its store description.

• Accessing and reviewing trade history (markets.com help centre)
• Extracting your account statement (markets.com help centre)
• Adding MetaTrader 4 or 5 to your account (markets.com help centre)
• markets.com group and regulatory functions

Mapped by the OpenBanking Studio integration desk · 2026-06-04

Questions an integrator tends to ask

Can you read both my MT5 sub-accounts and my native markets.com platform balance in one feed?

Yes. We normalize the MetaTrader server protocol used by MT4/MT5 accounts and the My Portal session used by the native platform into one schema, so several sub-accounts under a single login reconcile into a single positions-and-balance feed.

Does pulling this data require open-banking or AIS consent?

No. A CFD trading account is not a payment account, so Account Information Services rules do not cover it. The basis is your own authenticated access to the account and, for the Cyprus-regulated entity, your GDPR right of access and portability over the records Safecap holds.

How granular is the closed-positions history compared with the downloadable PDF statement?

The Closed Positions report under Account then Reports gives per-trade rows — open and close time, price and realized profit. The account statement PDF covers a chosen period at ledger level: balance, equity, deposits, withdrawals and fees. We parse both and join them on trade and value dates.

Which markets.com entity's records are we integrating — Cyprus, South Africa or SVG?

That depends on the entity your account opened under: Safecap Investments (CySEC), Markets South Africa (FSCA), or Markets International in Saint Vincent and the Grenadines. We confirm the operating entity during onboarding because statement formats and base currencies differ, and we scope the integration to it.

Source for the statement-export and positions reads lands in a runnable repo inside one to two weeks. Take it as a fixed delivery from $300, paid only once it runs against your own account, or call our hosted endpoints and pay per request with nothing upfront. Tell us the account types you hold and the data you need at our contact page and we scope it from there.