Background: wealthAPI allows you to seamlessly plug-in family-office grade wealth management functionalities into your existing offering. For the perspective of an end-user, data consistency is important. We thus offer our partners to “bring their own data” to allow for a frictionless integration into their existing ecosystem.

Additionally, this might come with a huge cost advantage, as our partners typically already hold data licenses which they would love to re-use.

The following data entities are essential to the service and should thus be provided.

We are able to handle any quote data provider, including crypto currencies. It is also up to you, which stock exchanges you would like to include.

Quote data contains the following entities:

A meta description of a security (typically an ISIN). This should come with

• the name of the security

• the type (e.g. a stock, bond or ETF)

• if it denotes in percent or currency

This data is often delivered with the “Securities” request.

• a region classification

• a sector classification

We will map your classification internally into the GICS standard thereby providing interoperability.

• a series of end-of-day prices, in daily resolution

  • high, low, last and volume are optimal, but we can also just work with “last”

• optimally the series range back for at least 10 - 15 years

• data should be delivered split adjusted as well as non-split adjusted

• no adjustment for capital measures and dividends must be done

• the currency of the timeseries should be provided

We will query the full timeseries only once, then the data will be cached on our side to keep load off your APIs. Also, we will refresh data for the last 30 days once per week to account for gaps that might have happened due to connectivity issues, quote provider issues or other technical issues.

The current valuation of a security, on a certain stock exchange. We typically expect your API to deliver the values currency, high, low, bid, ask and last; each with a timestamp. If not available, we can map whatever your API provides to our internal data structures.

If you are using our “dividend planner” module, then dividend data is essential as well.

A timeseries of historic dividends for a given security (typically an ISIN). This should contain the fields

• amount

• pay date

• ex date

• currency

• is special (is this a special or a regular dividend)

• payment interval (optional)

A prediction-series of future dividend, typically derived from analyst consensus. Predictions should have the same datapoints as a historic time series; only with a future date.

• amount

• pay date

• ex date

• currency

• is special (is this a special or a regular dividend)

• payment interval (optional)

If no predictions are available, we will calculate this based on a linear model. See https://wealthapi.atlassian.net/wiki/spaces/PD/pages/618921990.

To reduce the number of daily API requests we highly recommend that you provide an endpoint listing the securities (typically a list of ISINs) that had recent data updates. This way our dividend data importer needs to only iterate over securities that have in fact new data.

You might want to bring your own fund and ETF classification data for a more consistent feeling. To enable fund and ETF “lookthrouhgs”, we use the following data points

• breakdown by regions; this is percent in country (e.g. 35 % US)

• breakdown by industries; is is percent by sector (e.g. 12 % Technology)

• breakdown by currencies; this is percent by currency (e.g. 40 % EUR, 60 % USD)

• Top 10 holdings

• (Optional) Full holdings

To reduce the number of daily API requests we highly recommend that you provide an endpoint listing the funds (typically a list of ISINs) that had recent data updates. This way our classification data importer needs to only iterate over securities that have in fact new data.

In case you would like to use our fundamental APIs, we can also include stock fundamentals. This might be useful if you would like to build on our existing frontend components. It is however totally fine and common to directly integrate your own existing stock fundamental APIs.