Reaching a TradeAll TR account's holdings and orders programmatically

TradeAll TR runs on Ak Yatırım's brokerage backend and signs members in with their Akbank credentials, which puts a live BIST and VİOP account a few authenticated calls past that login. Ak Yatırım is the regulated broker on record; TradeAll and TradeAll TR are its trademarks. That matters for an integration because the data you want — open positions, executed orders, leveraged VİOP contracts — is real account state on a licensed broker's servers, not a public quote feed. Our job is to reach it the way the member already can, under their consent, and hand back code that does it on a schedule.

The route we would actually take here is consent-based protocol integration: a logged-in session, replayed cleanly, against the portfolio and order surfaces. It survives front-end redesigns better than screen automation and gives you typed records instead of scraped HTML. A native or portal export keeps the lights on if a member can only share a statement file. More on why below.

What sits behind the Akbank login

These are the surfaces the app itself exposes to a signed-in investor, named the way TradeAll TR names them. Each maps to a record an integrator would normalize and sync.

Authorized ways into the data

Three routes genuinely apply to TradeAll TR. We set up access for whichever we run — the consenting account, any sandbox, and the paperwork are arranged with you during onboarding, not asked of you up front.

1. Consent-based protocol integration

We observe the authenticated session the member already uses — the Akbank SSO handoff, the brokerage token it mints, and the calls the app makes for portfolio, positions and orders — then rebuild those calls as a documented client. Reachable: nearly everything the member sees in-app. Effort: moderate, mostly in the auth chain. Durability: good, as long as we re-validate when the front end shifts. This is the route we recommend for TradeAll TR, because the value is in structured account state that only an authenticated session returns, and the Akbank login is a one-time mapping cost that pays off across every later sync.

2. User-consented session access

Where a team prefers not to persist replayed calls, the member authenticates through the integration under their own consent and we read the same surfaces live per request. Lighter to stand up, heavier per call, and well suited to one-off pulls or low-frequency reconciliation.

3. Native / portal export

Ak Yatırım's channels produce statement and research artifacts a member can export. Slower and coarser than the session routes, but a dependable backstop when consent for live access is narrow — useful as a reconciliation source rather than a primary feed.

What lands in your repo

Everything here is tied to TradeAll TR's actual surfaces, not a generic kit.

• An OpenAPI/Swagger spec covering the endpoints we map — portfolio, VİOP positions, order history, watchlists and quotes.
• A protocol and auth-flow report documenting the Akbank SSO step, the brokerage token exchange and the session/cookie chain as it behaves during the build.
• Runnable source in Python or Node.js for login, portfolio fetch, VİOP position fetch and order-history pull.
• A replay harness plus automated tests that run the client against captured fixtures, so a front-end change surfaces as a failing test instead of a silent gap.
• Interface documentation and KVKK-aware retention guidance for the records you store.

A positions call, sketched

Illustrative shape of the VİOP positions read, with the field names confirmed against the app's surfaces during the build. Constants such as host and token format are stand-ins until mapped on your engagement.

POST /brokerage/v1/viop/positions
Authorization: Bearer <brokerage_token from Akbank SSO exchange>
Content-Type: application/json

{ "accountId": "<member account>", "settlement": "T0" }

200 OK
{
  "positions": [
    {
      "contract": "F_XU0300625",   // VİOP index future, June expiry
      "direction": "LONG",
      "quantity": 4,
      "multiplier": 10,
      "avgPrice": 11042.5,
      "marginUsed": 18860.00,
      "unrealizedPnl": 1240.00,
      "quoteTier": "DELAYED"        // or "REALTIME" if entitled
    }
  ]
}

# error path the client must handle:
# 401 -> SSO token aged out  -> re-run Akbank handoff, retry once
# 409 -> entitlement missing -> downgrade quoteTier, flag to caller

Who regulates this, and how consent works

Brokerage activity here answers to the Capital Markets Board (SPK), with post-trade running through Borsa İstanbul, the central securities depository (MKK) and Takasbank for clearing and custody. Personal data falls under KVKK, Türkiye's data-protection law (Law No. 6698). One distinction shapes the build: Turkey's open-banking framework, set by the BDDK and the central bank under Law No. 6493, governs payment accounts — it does not reach into brokerage holdings. So the dependable basis for a TradeAll TR integration is the member's own written consent, scoped to the surfaces you need, with a defined expiry and a revocation path. We log access, keep consent records, minimize what we store, and work under NDA where the engagement calls for it.

What we plan around in the build

Two things about this app shape the engineering, and we handle both as part of the work.

• The SSO handoff. Authentication starts with Akbank, not Ak Yatırım, so there are two token lifetimes in play. We map the SSO-to-brokerage-token exchange and design the refresh around its expiry, so an intraday sync does not quietly drop after the first token ages out.
• Live versus delayed quotes. The app sells live market data as a paid add-on, which means a member's feed may be delayed or real-time depending on entitlement. We tag every quote with its tier so a downstream model never treats a delayed print as the live book.
• VİOP contract specs. Futures and options carry multiplier, expiry and margin that equities lack. We normalize them into a separate contract record so derivatives and BIST shares never collide in one schema, and we re-validate the mapping when the app's front end changes.

Pricing, and how a project runs

Source-code delivery starts at $300, billed only after the integration is in your hands and working to your satisfaction — you get the runnable client, the OpenAPI spec, the auth-flow report, tests and docs, and you own the code. If you would rather not host anything, the pay-per-call hosted API has no upfront fee: you call our endpoints for TradeAll TR and pay only for the calls you make. Either way the cycle is one to two weeks. Tell us the app and what you want from its data, and we arrange access and compliance with you. Start a project on the contact page.

Where teams point this

• A portfolio app consolidating a user's BIST and VİOP holdings alongside other brokers into one net-worth view.
• A tax or accounting tool exporting executed orders and dividends from the order history and corporate-events surfaces.
• A risk dashboard watching leveraged VİOP margin in near real time for a desk that trades through TradeAll TR.
• A research pipeline ingesting Ak Yatırım model-portfolio target prices and KAP news for signal work.

Keeping live data live

Market surfaces move fast and entitlements differ per member, so the client is built to fail loud, not stale. Quotes carry their tier. The auth refresh is scheduled around the SSO token, not guessed at. And the test fixtures double as a change detector: when Ak Yatırım reshapes a response, a test breaks and we ship a fix rather than letting a feed rot. Re-validation is part of how we keep an integration current, not an afterthought.

Interface evidence

Public store screenshots of TradeAll TR — tap to enlarge.

What we checked

Drafted on 6 June 2026 from the app's Play Store and App Store listings, Ak Yatırım's own model-portfolio and trademark pages, and the published positions of Türkiye's market and banking regulators. The surfaces named above come from the store descriptions; the regulatory split between brokerage oversight and payment-side open banking comes from the regulator and tracker sources below.

• TradeAll TR on Google Play
• TradeAll TR on the App Store
• Capital Markets Board of Türkiye (SPK)
• Open banking in Turkey — regulatory scope (BDDK / TCMB)

Mapped by the OpenBanking Studio integration desk · 6 June 2026.

Other Turkish brokerage apps in the same map

A consolidation layer rarely stops at one broker. These are real Borsa İstanbul-facing apps an integrator tends to encounter alongside TradeAll TR; we frame them as neighbours on the same map, not a ranking.

• Midas — SPK-licensed app for BIST shares and warrants plus US stocks and options, holding per-user portfolios and orders.
• Gedik Trader — Gedik Yatırım's platform for BIST indices, FX pairs, metals, equities and VİOP contracts.
• TradeMaster Mobile — İş Yatırım's app for account details, free live data and BIST equity and VİOP trading.
• QNB Invest — single-platform access to stocks, VİOP, forex, mutual funds and ETFs with smart order types.
• Garanti BBVA Yatırım — bank-linked brokerage holding investment accounts and BIST order flow.
• Yapı Kredi Yatırım — another bank-affiliated broker with portfolio and trading data behind a login.
• Matriks — market-data and analysis terminal widely used by Turkish traders for BIST and VİOP.
• Foreks — market-data app covering BIST, FX and commodities with watchlists and alerts.

Questions integrators ask about TradeAll TR

Does signing in through Akbank change how the integration is built?

Yes. TradeAll TR authenticates members with their Akbank credentials before handing off to Ak Yatırım's brokerage session, so the build maps that single-sign-on step first and keeps the brokerage token refreshed around its own expiry. We treat the handoff as one documented stage of the auth flow in the protocol report we ship.

Can the delivered code tell a real-time quote from a delayed one?

The app sells live market data as a paid add-on, so a member may be on delayed prices or on an entitled real-time feed. We model both tiers and tag each quote with its source, so a downstream system never mistakes a delayed print for the live book.

How are VİOP leveraged positions represented in the schema?

Futures and options on VİOP carry margin, multiplier and expiry fields that cash equities do not. We give them their own normalized contract record — instrument code, expiry, multiplier, position direction and margin — so derivatives and BIST shares stay distinct in one feed.

Which Turkish authority's rules shape a TradeAll TR integration?

Brokerage activity sits under the Capital Markets Board (SPK) and the Borsa İstanbul, MKK and Takasbank post-trade chain, while personal data is governed by KVKK (Law No. 6698). Turkey's payment-side open-banking rules under BDDK and the central bank do not extend to brokerage holdings, so the integration runs on the member's own documented consent.

If we only need VİOP position data and not the full portfolio, does that narrow the work?

It does. Scoping to VİOP positions and order history means fewer surfaces to map and a smaller schema, which usually shortens the one-to-two-week cycle. The app name and the surfaces you want are enough for us to size it.