My Stocks Portfolio API integration (OpenFinance & data sync)

Deliverables checklist

• OpenAPI 3.1 specification of every exposed endpoint
• Protocol & auth flow report (token lifecycle, sync handshake, CSV schema)
• Runnable Python or Node.js source for holdings, transactions and quotes
• Webhook receiver for price-alert and transaction events
• Test harness (pytest / vitest) plus sandbox fixtures
• Compliance notes: SEC market-data redistribution, GDPR data minimization

Engagement models

Two clean ways to engage so you only pay for what you use:

• Source code delivery from $300 — runnable adapter and full docs handed over; pay after acceptance.
• Pay-per-call hosted API — call our managed endpoints and pay per request; ideal for low-volume tooling or proof-of-concept dashboards.

1. Tax & capital-gains reporting

An accountant aggregates a client's positions across two My Stocks Portfolio portfolios and a brokerage statement. We push /transactions?from=&to= output, normalised to ISO-4217 and HMRC/IRS lot-matching rules, into the firm's tax engine. The new default-accounting-method field (LIFO / FIFO / average) flows through so cost-basis matches what the user sees in the app.

2. Multi-currency net-worth dashboard

A wealth platform pulls holdings + the app's FX rate every 15 minutes, converts to a single reporting currency, and renders the same 2-ring sector pie chart logic used in-app. The OpenFinance-style aggregation lets one user view US equities, LSE positions and BTC in a single allocation view.

3. Risk & concentration alerts

A risk engine subscribes to a webhook of price-alert events and recomputes Value-at-Risk whenever a position drifts past a threshold. Because alerts fire from the app's own logic, no separate quote feed needs to be reconciled.

4. Migration to an OpenFinance aggregator

A user moving from My Stocks Portfolio to Ghostfolio, Wealthfolio or Sharesight imports the full transaction history in one shot. Our parser maps the CSV schema (and the live API equivalent) to each target's import format including dividend reinvestment events.

5. Research backtesting on watchlists

A quant team feeds the user's watchlists plus historic OHLCV into a backtester, joining symbol metadata (exchange, currency, sector tag) so signals can be ranked against a personal universe rather than a generic index.

Auth: token exchange

POST /api/v1/peeksoft/auth/token
Content-Type: application/json

{
  "user_id": "ext-7421",
  "consent_id": "c_2026_05_10_a1",
  "scopes": ["holdings:read","tx:read","quotes:read"]
}

200 OK
{
  "access_token": "eyJhbGc...",
  "refresh_token": "rft_...",
  "expires_in": 3600
}

Holdings export

GET /api/v1/peeksoft/portfolios/{pid}/holdings
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "portfolio_id": "p_main",
  "report_currency": "USD",
  "as_of": "2026-05-10T12:00:00Z",
  "holdings": [
    {"symbol":"AAPL","exchange":"NASDAQ","qty":50,
     "avg_cost":141.22,"currency":"USD",
     "unrealized":1820.50,"weight_pct":18.7},
    {"symbol":"BTC","exchange":"CRYPTO","qty":0.42,
     "avg_cost":28110.00,"currency":"USD",
     "unrealized":4123.10,"weight_pct":9.4}
  ]
}

Webhook: price alert event

POST https://your-app.example.com/webhook
X-OFL-Signature: sha256=...

{
  "event":"price_alert.triggered",
  "alert_id":"al_99821",
  "symbol":"TSLA",
  "direction":"above",
  "threshold":280.00,
  "last_price":281.34,
  "fired_at":"2026-05-10T13:02:11Z"
}

// Recommended: respond 2xx within 5s,
// reconcile asynchronously, retry on 5xx.

Compliance & privacy

We integrate only with explicit user authorization or documented public endpoints. Personal data is processed under GDPR (EU) and CCPA (California) with retention windows configurable per deployment. Market-data redistribution respects exchange terms and US SEC / FINRA disclosure rules; EU venues are handled per MiFID II best-execution and reporting obligations. Crypto data flows reference the EU's MiCA framework and US FinCEN guidance for custodial vs non-custodial reporting. Every consent event is logged with a tamper-evident hash so audits are straightforward.

Data flow / architecture

A typical pipeline looks like this:

• Client app (My Stocks Portfolio) — origin of holdings, transactions, alerts.
• Protocol adapter — performs auth handshake, paging, schema normalization.
• Storage & cache — Postgres for canonical state, Redis for hot quotes & FX.
• API gateway — exposes REST/JSON to your backend and signs outbound webhooks.

Sharesight

Award-winning performance and tax-reporting platform tracking equities and ETFs across 60+ exchanges. Users often want one-shot import of a My Stocks Portfolio CSV plus ongoing transaction sync.

Empower (Personal Capital)

Free dashboard for net worth, retirement and investment tracking. Integrations typically merge Empower's account-level data with the per-symbol detail My Stocks Portfolio provides.

Delta Investment Tracker

Multi-asset tracker popular with crypto-heavy portfolios. Bridging it with My Stocks Portfolio gives users a single transaction ledger across TradFi and digital assets.

Snowball Analytics

Dividend-focused tracker. Pairs naturally with the dividend events exported from My Stocks Portfolio when users want forecasted income calendars.

Kubera

Modern wealth tracker covering stocks, crypto, real estate and private holdings. Often imports My Stocks Portfolio holdings to consolidate liquid investments in one balance sheet.

Stock Rover

Research-heavy desktop platform. Users typically push watchlists from My Stocks Portfolio into Stock Rover for screening and back-testing.

Yahoo Finance Portfolio

Long-running web/mobile tracker. Many users keep Yahoo for news + alerts and My Stocks Portfolio for cost-basis accuracy; the two are commonly synced.

Ghostfolio & Wealthfolio

Open-source, privacy-first portfolio trackers. Self-hosters frequently ask for an adapter that ingests My Stocks Portfolio exports into a Ghostfolio or Wealthfolio database.

Seeking Alpha & M1 Finance

Seeking Alpha covers research and rating signals; M1 Finance handles brokerage and pie-based portfolios. Both pair well with the holdings layer that My Stocks Portfolio already maintains.

About OpenFinance Lab

We are an independent studio focused on App protocol analysis and authorized API integration. Engineers on the team have shipped trading systems, market-data feeds and OpenBanking adapters for fintech clients across North America, EMEA and APAC. We specialise in turning consumer finance apps — like My Stocks Portfolio — into reliable backend data sources without breaking their compliance posture.

• Personal finance, brokerage, crypto and OpenBanking integrations
• OAuth / token / cookie protocol analysis and renewal logic
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: scope → analysis → build → validation → compliance
• Source code delivery from $300 — runnable adapter and full docs handed over; pay after acceptance
• Pay-per-call hosted API — no upfront fee; ideal for low-volume tools

Contact

Tell us the target app and the data you actually need (holdings, transactions, alerts, watchlists). We'll come back with scope, timeline and price.

Open contact page

Engagement workflow

1. Scope confirmation: which portfolios and which data types (login, holdings, transactions, alerts).
2. Protocol analysis & OpenAPI design (2–5 business days).
3. Build and internal validation against fixtures (3–8 business days).
4. Docs, samples, test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; exchange or third-party approvals may extend the schedule.

FAQ

What data can you actually pull out of My Stocks Portfolio?

How do you handle the CSV export workflow vs a live API?

What about compliance for stock and crypto data?

How long until I get a working build?