MASSARIdocsRequest access

ETF overlap

GET/v1/funds/{symbol}/overlap/{other}Promised whole

Shared holdings and overlapping weight between two funds.

Parameters

  • symbolpathrequired

    Ticker symbol, case-insensitive.

  • otherpathrequired

    The second fund to compare against.

Response contract

Every field in the response is part of the contract.

Response fields

The top level keys a live response actually returned, read off the API rather than written down here.

etf_aetf_boverlap_countoverlap_weight_aoverlap_weight_bshared_holdings

How this was verified

Called against 2 different subjects on the live API. Every field it returned, at every level, was compared with the contract above. Last checked August 18, 2026.

Request

curl "https://api.massari.ai/v1/funds/SPY/overlap/QQQ" \
  -H "Authorization: Bearer $MASSARI_TOKEN"

Example response

{
  "etf_a": "SPY",
  "etf_b": "QQQ",
  "overlap_count": 86,
  "overlap_weight_a": 0.5021,
  "overlap_weight_b": 0.9173,
  "shared_holdings": [
    {
      "holding_symbol": "NVDA",
      "holding_name": "NVDA",
      "weight_a": 0.08012,
      "weight_b": 0.08988
    },
    {
      "holding_symbol": "AAPL",
      "holding_name": "AAPL",
      "weight_a": 0.06485,
      "weight_b": 0.07152
    }
  ]
}

A real response from the live API, captured August 18, 2026. This one is CUT: long arrays, wide objects and long strings were trimmed to keep it readable, so treat it as a sample of the shape rather than all of it. Either way it is valid JSON.

Book a meeting