ETF flows, the day's summary

What the US ETFs read daily from their issuers' files bought and sold, security by security, from the change in shares held between each fund's previous file and its file of date, each file placed at the market close it reflects: the largest net additions and reductions by value, in percent and beyond the funds' own growth, the securities that entered or exited funds tracking the same index, the corporate actions, and each of the last 20 closes. Its CSV twin, /api/v1/flows.csv, lists every security moved on date. A change in shares held mixes the creations and redemptions of a fund's own shares with its rebalancing: read beyond_growth for the second. Only the funds read daily from their issuers are counted, never the funds known from SEC filings, and only common shares: futures, options and short positions are left out. A split, a bonus issue or a stock dividend, a count in other units, a line a file dropped for a day, a change of ticker and the lines a merger or a spin-off moved are left out as no trade. A sum is published only when three or more funds make it and no one fund more than 80% of it; withheld says why one is null. Feeds: /feeds/flows.xml, /feeds/fund/{ticker}.xml, /feeds/stock/{ticker}.xml (RSS 2.0). Not under CC BY 4.0: the history terms apply. A feed reader may poll the feeds; fetching the shards or many securities' answers on a schedule to keep them is systematic extraction.

get/flows.json

Request

  • Base URL: https://tickerinside.com/api/v1
  • URL: https://tickerinside.com/api/v1/flows.json
  • Auth: none required

Response

The file. The example is a real answer, shortened: long lists and maps keep their first entries.

datestring nullable required

The market close of the figures: the newest close that nine in ten of the funds counted have a file of. Each file is placed at the close it reflects (Invesco dates a Friday's file on the Saturday), and each fund's change runs from its previous file to its file of this close.

newest_filestring nullable required

The newest close a file read reflects. A close is published once every fund still publishing has a file of it or of a later close, so date can be older.

first_datestring nullable required

The first close with a counted change: the first files carrying share counts in today's keys.

methodstring required

The method of the figures, ti-flows/1.

file_gapsinteger required

How many lines the window leaves out because an issuer's file dropped them for a day and they came back with the same count.

securitystring required

The address of one security's flows, with {ticker} to fill.

csvstring required

Every security moved on date, one row each, largest net value first.

feedstring required

This summary as an RSS feed, one item per complete close.

feed_fundstring required

One fund's holdings changes as an RSS feed, from its history, with {ticker} to fill.

feed_stockstring required

One security's flows as an RSS feed, with {ticker} to fill.

notestring required

How to read the figures.

cite_asstring required

A citation line: the close and this file's address.

cite_htmlstring required

The credit as HTML: a link to this file, then its address.

docsstring required

Where the file is documented.

licensestring required

The terms the flows are published under: TickerInside's history terms, not CC BY 4.0, as they are computed from the archive.

termsstring required

The terms in full, on the legal notice.

attributionstring required

How to credit it, then what the history terms allow.

Changes

No recorded changes to this operation across all 1 revision of this API.