It returns tabular, list-based data for up to 100 investments in a single request. It is designed for grid and list views such as watchlists, comparison tables and dashboards, and returns one flat row for each investment, across funds, ETFs and equities. See Core Concepts.

The API has two endpoints.

Use the base URL for your region.

• Americas: https://www.us-api.morningstar.com
• APAC: https://www.apac-api.morningstar.com
• EMEA: https://www.emea-api.morningstar.com

Yes. The whole list is returned in the response to the same request.

No. The Investment List API returns data for investments that you already know. To find investments that match criteria, use one of the Screener APIs. For a historical series, use the Time Series API.

Request a token from POST /token/oauth, then send it on every other request in the Authorization header as Bearer {token}. See Authentication.

A token is valid for 60 minutes and can be reused across requests during that time. Long-running jobs must request a new token before it expires, and retry any request that returns 401 Unauthorized.

From 1 to 100 per request. To retrieve more, split them across several requests.

Morningstar Performance ID (the default), ISIN, fund code, Morningstar Security ID, CUSIP, Morningstar ID and trading symbol. Set idType to say which one an id is. See Request an Investment List.

Not for Morningstar Performance IDs, which are the default. For any other identifier, set idType on that entry, for example isin or tradingSymbol.

Yes. Each entry has its own idType.

"investments": [
  { "id": "0P0000004Y" },
  { "id": "US5434957743", "idType": "isin" }
]

Add lookup details to that entry to narrow the match: exchangeCountry, domicile, baseCurrency or exchangeId. Each entry has its own details. See Request an Investment List.

The request still succeeds, but no row is returned for that identifier. The identifier is listed in metadata.messages. See Work with Results.

Call the data points endpoint. It lists every data point with its name, any alias and its type. See Explore Data Points.

Up to 50 per request. They become the columns of your list.

Yes. Every row has a performanceId, whether or not you request it.

Yes, where a data point has one. For example, performanceId is the alias of instrumentIdentifiers.performanceId, and you can use either in dataPoints.

If you aren't entitled to a data point for an investment, the row is returned without it, and metadata.messages lists the data point. See Work with Results.

Use the sort array. You can sort by up to 2 data points, applied in order, and each must also be in dataPoints. If you don't set a sort order, rows are in ascending performance ID order. See Request an Investment List.

No. The rows for all matched investments come back in a single response, up to the 100 investments you asked for.

Match on performanceId, not on the position of a row, because investments that can't be matched return no row. If you identified investments with something other than a performance ID, add a data point that returns that identifier, such as basicReference.isin. See Work with Results.

No. Unmatched identifiers return no row, and data points you aren't entitled to are left out of a row. Both are reported in metadata.messages, so always check it.

They set the language and currency of the results. Both are optional.

It is a unique identifier for the request. It is returned in the response metadata, and in error responses. Include it if you contact support.