Snowball Analytics API integration & dividend OpenFinance services

Portfolio consolidation API

Merge multiple brokerage accounts into one portfolio object: account list, holding lots, currency, weights, and asset class. Useful for wealth dashboards and family-office reporting where users pull from Charles Schwab, Interactive Brokers, Trading 212, Tinkoff-style brokers, and Binance simultaneously.

Dividend & coupon calendar

Endpoint returns expected payments, actual receipts, ex-dividend dates, payment dates, withholding tax, and 5-year payout projections. Drives passive-income forecasting tools and FIRE goal trackers that need clean dividend cash-flow streams.

Transactions & broker fees

Itemized buy/sell, dividends, splits, mergers, fees, and currency conversions, with broker-of-record tagging. Powers reconciliation against your own ledger or accounting platform without manually parsing PDF statements.

Returns analytics & TWR

Optimized Time-Weighted Return per asset and per portfolio (the 2025 calculation pipeline handles large multi-thousand-row portfolios), plus annualized return, MWR, and currency-adjusted P&L for tax and compliance-grade analysis.

Custom & non-listed assets

Loans, deposits, real estate, private equity, and other off-exchange holdings can be added programmatically — including the 2025 ability to create transactions for custom assets — so off-broker wealth lands in the same dataset.

Dividend Rating signal

The 13-parameter Dividend Rating is exposed as a per-ticker score with sub-component breakdown, suitable for screening pipelines, watchlists, and AI-driven income-portfolio construction.

1. Family-office consolidation

Context: a multi-member household holds accounts at Interactive Brokers, Trading 212, and a domestic broker, plus a rental property and a fixed-deposit ladder. Snowball Analytics aggregates all of these. Our connector exposes a single /portfolio/snapshot response containing brokerage holdings, custom-asset valuations, and pending dividend payouts — mapped to OpenFinance-style account & balance objects so a family-office CRM or treasury tool can ingest them in minutes.

2. Dividend-income forecasting service

Context: a robo-advisor wants to show users projected income for the next 12 and 36 months. We pull the dividend calendar (confirmed + estimated) and Dividend Rating, then expose /dividends/forecast?horizon=36m. Output includes per-ticker contribution, FX exposure, and risk flags driven by Snowball's 13-parameter rating — all aligned to OpenBanking dividend-income data primitives.

3. Tax & compliance reporting

Context: an accountant needs annualized returns, currency-adjusted P&L, and full transaction history for a cross-border investor. We expose authorized /transactions and /twr endpoints with date range, currency, and broker filters. Outputs map to OECD CRS / FATCA-ready reports and feed downstream tax tools that already speak OpenFinance JSON schemas.

4. ETF and dividend-ETF screener

Context: a fintech app builds an "income-quality" screener. We surface Snowball's Dividend Rating and historical payout consistency through /instruments/{ticker}/dividend-rating, joined to the user's holdings so the app can flag risky dividend payers already in the portfolio. Combines OpenData market signals with permissioned investment-account data.

5. Multi-broker reconciliation pipeline

Context: an enterprise treasury team wants nightly reconciliation between trade tickets and Snowball's normalized data. We deliver an event-driven /webhook/transactions.synced + idempotent /transactions?since=… endpoint, plus deduplication by (broker_id, external_trade_id), so back-office systems get clean, replayable streams instead of one-off CSV exports.

Authorized session establishment

POST /api/v1/snowball/session
Content-Type: application/json
Authorization: Bearer <PARTNER_API_KEY>

{
  "user_ref": "u_8b3d09",
  "scopes": ["portfolio.read", "dividends.read", "transactions.read"],
  "broker_links": ["snaptrade:ibkr", "yodlee:schwab"]
}

Response 200:
{
  "session_id": "sess_3f...",
  "expires_at": "2026-04-29T10:45:00Z",
  "consent_id": "cns_7c..."
}

Dividend calendar query

GET /api/v1/snowball/dividends?from=2026-04-01&to=2026-12-31&ccy=USD
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: cns_7c...

Response 200:
{
  "currency": "USD",
  "events": [
    {
      "ticker": "JNJ",
      "ex_date": "2026-05-22",
      "pay_date": "2026-06-10",
      "amount": 1.24,
      "status": "confirmed",
      "drip": true,
      "rating": { "score": 86, "factors": 13 }
    }
  ],
  "next_page": null
}

Transactions webhook

POST /your-app/webhooks/snowball
X-Snowball-Signature: t=...,v1=...

{
  "event": "transactions.synced",
  "session_id": "sess_3f...",
  "broker": "snaptrade:ibkr",
  "delta_count": 34,
  "since": "2026-04-27T00:00:00Z"
}

// Verify signature with shared secret, then call:
// GET /api/v1/snowball/transactions?since=2026-04-27T00:00:00Z
// Idempotency-Key: snowball-2026-04-27-ibkr

Regulatory alignment

Snowball Analytics handles personally identifiable financial data, so integrations must respect GDPR for EU users (lawful basis, data-subject access rights, retention limits), PSD2 / SCA patterns where account information services are involved, and SEC / FINRA custody and recordkeeping considerations for US brokers. Where SnapTrade or Yodlee underpins the connection, we inherit their SOC 2 Type II controls and propagate consent metadata to your stack.

Privacy-by-design

We do not require personal identity from end users beyond what Snowball itself stores; we minimize broker credentials by relying on tokenized OAuth links from SnapTrade/Yodlee/IBKR native rather than raw passwords. Consent records, access logs, and revocation events are persisted for audit and can be exported as JSON for your DPO.

Deliverables checklist

• OpenAPI / Swagger spec for portfolio, dividends, transactions, TWR
• Protocol & auth flow report covering OAuth tokens, consent IDs, refresh, and revocation
• Runnable source (Python and Node.js) for ingestion, normalization, and webhook handling
• Postman collection plus pytest/Jest test suite for regression on broker links
• Compliance briefing: GDPR retention, PSD2 SCA touchpoints, SOC 2 inheritance from SnapTrade/Yodlee
• Operational runbook: backfill, idempotent replays, and broker-specific quirks

Engagement options

• Source-code delivery from $300 — runnable API source plus documentation; you pay after delivery upon satisfaction
• Pay-per-call hosted API — no upfront cost; ideal for teams validating dividend-income features before committing
• Custom modules — Dividend Rating exposure, FX-adjusted TWR, or webhooks for transactions/dividends
• NDAs, scoped data agreements, and on-prem deployment available on request

Who we are

We are an independent technical studio specializing in App interface integration and authorized API integration. Team members come from banks, brokerages, and fintech infrastructure providers, with hands-on experience in protocol analysis, OpenFinance flows, and cloud delivery. We have shipped integrations against investment platforms, payment rails, and data aggregators including SnapTrade- and Yodlee-style stacks.

How we work

For each project we walk through scope, identify which Snowball Analytics surfaces (holdings, dividend calendar, transactions, TWR, custom assets) you actually need, then deliver runnable source code or hosted endpoints. We follow a simple principle: only authorized or documented public APIs, full audit logs, and data minimization by default. No fragile screen scraping, no shared raw credentials.

Contact

To request a quote or share your target requirements (data types, brokers, expected call volume, deployment region), open our contact page:

Go to contact page

Workflow

1. Scope confirmation: which Snowball data (dividends, holdings, transactions, TWR, custom assets) and which brokers
2. Protocol & auth analysis: OAuth/token chain, consent model, broker-specific quirks (2–5 business days)
3. Build & internal validation: connector, normalization, webhooks, replay logic (3–8 business days)
4. Documentation, sample clients, Postman, and tests (1–2 business days)
5. First delivery typically lands in 5–15 business days; multi-broker rollouts may extend timelines

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?