It returns historical time series data for investments, such as prices, returns, yields, ratings, fees and sustainability metrics. Each data point has its own endpoint, grouped into categories, and each request retrieves one data point for up to 25 investments. See Core Concepts.

Every endpoint is a GET that follows the same pattern.

GET /direct-web-services/time-series/v1/{category}/{data-point}/{ids}

The category and data point select what you retrieve, and {ids} holds the investments. Use the base URL for your region, as described in Getting Started. To find the endpoint you need, see Choose a Data Point.

Yes. The data is returned in the response to the same request.

Yes. You can create an account to get credentials and test the endpoints. Trial responses are limited to a sample of real data from a sample universe. For full data coverage and production access, contact Morningstar sales. See Getting Started.

Authentication has two steps. First, request a token from POST /token/oauth, using your Client ID and Client Secret as HTTP Basic credentials. Then send the token on every other request in the Authorization header as Bearer {token}. See Getting Started.

Create an application in your portal profile. The application issues the Client ID and Client Secret. They are separate from the username and password you use to log in to Morningstar for Developers.

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.

There are several hundred data points in eight categories. You can browse by category, search by name, or use the naming patterns to tell similar data points apart. See Choose a Data Point.

No. Each request retrieves one data point. To retrieve several, make one request for each data point.

Some data points are available under more than one category, and each category has its own endpoint. Examples are monthly-return in performance and fund-research, and daily-closing-price in reference and performance. Read the description of each endpoint before you choose between them. See Choose a Data Point.

Standard data points return values from stored data and use only the general request parameters. Computed data points calculate their values when you make the request, and accept extra parameters that control the calculation. The computed data points are return, cumulative-return, rolling-return, growth and price. See Core Concepts.

The API reference lists some performance data points in a separate In Trial group, including growth, price, monthly-return and quarterly-return. See Choose a Data Point.

A maximum of 25 per request. To retrieve more, split them across several requests.

Morningstar Performance ID (the default), Morningstar Security ID, MSID, ISIN, CUSIP and trading symbol. You can also pass category IDs, which must be URL-encoded. See Specify Investments.

Yes. Use idTypes to say what each value is. The list lines up with ids by position, empty entries default to performanceId, and trailing commas are omitted.

GET /direct-web-services/time-series/v1/performance/daily-price/US2562191062,MDLOX,0P00006W6Q
  ?idTypes=isin,tradingSymbol

Use the lookup filters baseCurrency, domicile, exchangeCountry and exchangeId to narrow the match. Each is a list that lines up with ids by position. The lookup values that were applied are returned in the metadata of each investment. See Specify Investments.

The request still succeeds, but no data is returned for that investment. The unmatched identifiers are listed in metadata.messages in the response. See Work with Results.

daily (the default), weekly, monthly, quarterly and annually. Set the frequency with the frequency parameter. See Set the Time Range.

You can use one of three approaches.

• Pass startDate and endDate in yyyy-MM-dd format.
• Pass timePeriod and timePeriodUnit (days, months or years) for a relative window.
• Set sinceInception to true to request data since inception.

See Set the Time Range.

sinceInception overrides timePeriod, timePeriodUnit, startDate and endDate. timePeriod and timePeriodUnit override startDate and endDate.

The maximum lookback depends on the frequency and the observation type.

Requests that go further back must be split into several requests.

Set sinceInception to true. The API returns data from the start of the investment's history, or from the maximum supported lookback, to the end date. sinceInception isn't supported for multivariate data points such as daily-ohlcv.

Set applyEarliestCommonDate to true. The start of every time series moves to the latest inception date among the requested investments. See Set the Time Range.

Yes. Use the currencyId parameter. The default, BAS, returns data in the investment's base currency. See Request Time Series Data.

It sets the performance stream used in a computed calculation: total (the default), market or gross. You can pass a second value as a fallback that is used if the first returns no data. The response returns the performanceType that was applied. See Configure Computed Data Points.

Use the rolling-return data point. Set windowSize for the length of the window and stepSize for how far it moves between calculations.

GET /direct-web-services/time-series/v1/performance/rolling-return/0P00000CSY
  ?startDate=2015-01-01
  &endDate=2024-12-31
  &frequency=monthly
  &windowSize=12
  &stepSize=1

Each computed data point accepts a different set of parameters. See the table in Configure Computed Data Points.

The response has an investments array, with one object for each investment that returned data, and a metadata object. Each investment has identifiers, a timeSeries object and metadata. See Work with Results.

Use the dataPoint value in each timeSeries object. Almost every data point returns a date and a single value. Only daily-ohlcv returns several values per date. See Work with Results.

No. If an identifier can't be matched, the request still returns 200, and the unmatched identifiers are listed in metadata.messages. Always check metadata.messages.

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.