Factset Formula API
Use FactSet's flexible, formula-based API to retrieve data from almost all available content sets FactSet offers through FactSet's FQL and Screening formulas.
OpenAPI Specification
openapi: 3.0.0
info:
version: 1.7.1
title: FactSet Formula API
description: >2
**FactSet Formula API**
FactSet’s Formula API is a modern, flexible, formula-based API that enables
users to access FactSet’s wide range of financial data and content. The API
offers two endpoints, one optimized for time-series analysis and one
designed for cross-sectional analysis, providing users a simplified
interface into FactSet’s expansive offering. By providing two endpoints, it
allows for the optimization of user workflows, while reducing complexity.
Leverage the power and flexibility of the Formula API to -
* Pull data from across most content sets that a user has access to in a single request
* Include business logic and mathematical operations in request
* Submit a dynamic universe in both endpoints
* Return the fsymId to easily combine with other FactSet content / products
* Set the trading calendar
* Define custom display names
**Formula API Request Builder**
The Formula API Request Builder provides users everything they need to form
a Formula API request. In the Request Builder, you can select identifiers,
build a universe expression, select FQL or Screening formulas, easily apply
business logic and mathematical functions to the FQL or Screening formulas,
specify optional parameters, and construct a GET or POST request. The
Request Builder eliminates the need to have previous FQL and Screening
knowledge and allows you to quickly find your desired data items and form
the request.
The Formula API Request Builder can be accessed by navigating to
[https://developer.factset.com/formula-api-request-builder](https://developer.factset.com/formula-api-request-builder)
and logging in using your FactSet.net ID. When using the Request Builder to
construct requests for the one of the Formula API's endpoints, be sure to
toggle to the correct endpoint at the top of the page.
**How to Check the Health and Availability of the Formula API**
Please use the below endpoint to check the health and availability of the
Formula API. You must be authorized for this API to use the Health endpoint.
[https://api.factset.com/formula-api/health](https://api.factset.com/formula-api/health)
**How to Programmatically Download API Specification File**
You can download the FactSet Formula API Specification File in .yaml. using
the "Download Spec" button to the right of the version number. This
specification can then be used for Codegen to create your own SDKs.
servers:
- description: Production
url: https://api.factset.com/formula-api
security:
- BasicAuth: []
paths:
/v1/time-series:
get:
summary: >-
Factset Retrieve data items (FQL formulas) for a list of identifiers or defined universe.
description: >
The `/time-series` endpoint is closely aligned with FactSet’s powerful
data retrieval language **FactSet Query Language (FQL)** which is
optimized for time-series analysis. FQL can also perform sophisticated
statistical, mathematical, logical, and other complex operations on the
data.
This endpoint has a unique **TIMESERIES** data object that pairs the requested data with FactSet provided dates. This helps reduce the need for additional data requests and reduces the work required by users.
The `/time-series` endpoint supports Long Running asynchronous requests
up to **20 minutes** via the `batch` parameter. *This feature is
available to Individual Users subscribed to the Performance Package and
Performance Package Plus Performance Tiers and all Production Users. If
you are unsure which Performance Tier you are subscribed to or you would
like to gain access to the batch capabilities, please contact your
FactSet Account Team or "Report Issue" above and our support teams can
assist.*
tags:
- Time Series
operationId: getTimeSeriesData
parameters:
- $ref: '#/components/parameters/ids'
- $ref: '#/components/parameters/symbolType'
- $ref: '#/components/parameters/universe'
- $ref: '#/components/parameters/universeType_time_series'
- $ref: '#/components/parameters/formulas_time_series'
- $ref: '#/components/parameters/calendar_time_series'
- $ref: '#/components/parameters/fsymId_time_series'
- $ref: '#/components/parameters/displayName_time_series'
- $ref: '#/components/parameters/flatten_time_series'
- $ref: '#/components/parameters/dates_time_series'
- $ref: '#/components/parameters/batch'
responses:
'200':
description: >-
Gets an array of `Response Objects` for a list of IDs and FQL
formulas.
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$ref: '#/components/headers/api-supported-versions'
api-deprecated-versions:
$ref: '#/components/headers/api-deprecated-versions'
chain-id:
$ref: '#/components/headers/chain-id'
X-RateLimit-Limit-second:
$ref: '#/components/headers/X-RateLimit-Limit-second'
X-RateLimit-Remaining-second:
$ref: '#/components/headers/X-RateLimit-Remaining-second'
X-RateLimit-Limit-day:
$ref: '#/components/headers/X-RateLimit-Limit-day'
X-RateLimit-Remaining-day:
$ref: '#/components/headers/X-RateLimit-Remaining-day'
content:
application/json:
schema:
$ref: '#/components/schemas/time_series_response'
examples:
Single Id and Single Data Item:
$ref: '#/components/examples/time-series-singleId-singleItem'
Single Id and Single Data Item with fsymId=Y:
$ref: '#/components/examples/time-series-singleId-singleItem-fsymId'
Multiple Ids and Multiple Data Items with SEVENDAY Calendar:
$ref: '#/components/examples/time-series-multipleId-multipleItem'
Multiple Ids and Multiple Data Items with flatten=Y:
$ref: >-
#/components/examples/time-series-multipleId-multipleItem-flatten
Multiple Ids and Multiple Calculated Data Items:
$ref: >-
#/components/examples/time-series-multipleId-multipleCalculatedItem
Small Universe and Single Data Item:
$ref: '#/components/examples/time-series-smallUniv-singleItem'
Debt Universe and Multiple Data Items:
$ref: '#/components/examples/time-series-debtUniv-multipleItem'
'202':
description: Batch request has been accepted.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Request Accepted:
$ref: '#/components/examples/BatchStatusAcceptedResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'405':
$ref: '#/components/responses/405'
'406':
$ref: '#/components/responses/406'
'408':
$ref: '#/components/responses/408'
'415':
$ref: '#/components/responses/415'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
post:
summary: >-
Factset Retrieve data items (FQL formulas) for a list of identifiers or defined universe.
description: >
The `/time-series` endpoint is closely aligned with FactSet’s powerful
data retrieval language **FactSet Query Language (FQL)** which is
optimized for time-series analysis. FQL can also perform sophisticated
statistical, mathematical, logical, and other complex operations on the
data.
This endpoint has a unique **TIMESERIES** data object that pairs the requested data with FactSet provided dates. This helps reduce the need for additional data requests and reduces the work required by users.
The `/time-series` endpoint supports Long Running asynchronous requests
up to **20 minutes** via the `batch` parameter. *This feature is
available to Individual Users subscribed to the Performance Package and
Performance Package Plus Performance Tiers and all Production Users. If
you are unsure which Performance Tier you are subscribed to or you would
like to gain access to the batch capabilities, please contact your
FactSet Account Team or "Report Issue" above and our support teams can
assist.*
tags:
- Time Series
operationId: getTimeSeriesDataForList
responses:
'200':
description: >-
Gets an array of `Response Objects` for a list of IDs and FQL
formulas.
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$ref: '#/components/headers/api-supported-versions'
api-deprecated-versions:
$ref: '#/components/headers/api-deprecated-versions'
chain-id:
$ref: '#/components/headers/chain-id'
X-RateLimit-Limit-second:
$ref: '#/components/headers/X-RateLimit-Limit-second'
X-RateLimit-Remaining-second:
$ref: '#/components/headers/X-RateLimit-Remaining-second'
X-RateLimit-Limit-day:
$ref: '#/components/headers/X-RateLimit-Limit-day'
X-RateLimit-Remaining-day:
$ref: '#/components/headers/X-RateLimit-Remaining-day'
content:
application/json:
schema:
$ref: '#/components/schemas/time_series_response'
examples:
Single Id and Single Data Item:
$ref: '#/components/examples/time-series-singleId-singleItem'
Single Id and Single Data Item with fsymId=Y:
$ref: '#/components/examples/time-series-singleId-singleItem-fsymId'
Multiple Ids and Multiple Data Items with SEVENDAY Calendar:
$ref: '#/components/examples/time-series-multipleId-multipleItem'
Multiple Ids and Multiple Data Items with flatten=Y:
$ref: >-
#/components/examples/time-series-multipleId-multipleItem-flatten
Multiple Ids and Multiple Calculated Data Items:
$ref: >-
#/components/examples/time-series-multipleId-multipleCalculatedItem
Small Universe and Single Data Item:
$ref: '#/components/examples/time-series-smallUniv-singleItem'
Debt Universe and Multiple Data Items:
$ref: '#/components/examples/time-series-debtUniv-multipleItem'
'202':
description: Batch request has been accepted.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Request Accepted:
$ref: '#/components/examples/BatchStatusAcceptedResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'405':
$ref: '#/components/responses/405'
'406':
$ref: '#/components/responses/406'
'408':
$ref: '#/components/responses/408'
'415':
$ref: '#/components/responses/415'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
requestBody:
$ref: '#/components/requestBodies/time-series-postBody'
/v1/cross-sectional:
get:
summary: >-
Factset Retrieve data items (Screening formulas) for a list of identifiers or defined universe.
description: >
The `/cross-sectional` endpoint is closely aligned with FactSet’s
powerful data retrieval **Screening language** which is optimized for
analysis of data items at single point in time for different entities
and is extremely efficient for large universes.
The `/cross-sectional` endpoint supports Long Running asynchronous
requests up to **10 minutes** via the `batch` parameter. *This feature
is available to Individual Users subscribed to the Performance Package
and Performance Package Plus Performance Tiers and all Production Users.
If you are unsure which Performance Tier you are subscribed to or you
would like to gain access to the batch capabilities, please contact your
FactSet Account Team or "Report Issue" above and our support teams can
assist.*
***
### Iterated Cross-Sectional Functionality
This endpoint supports the ability to automatically iterate through
different cross sections over time. The **Iterated Cross-Sectional
Functionality (ICSF)** expands the Cross-Sectional endpoint to support
retrieving data items for *multiple dates*, allowing users to take
advantage of the Screening engine’s efficiency even when history is
required.
Use the parameters `startDate`, `endDate`, and `frequency` in the
Cross-Sectional endpoint to provide your desired dates. Specify “0” in
date argument of the Screening formulas provided in the formulas
parameter and/or the universe parameter. Lastly, the Iterated
Cross-Sectional Functionality is required to run as a `batch` request.
Therefore, the batch parameter must be set to “Y”.
Access to backtesting and batch functionality is required to leverage
the Iterated Cross-Sectional Functionality.
**When to use ICSF:**
The ICSF can offer better performance than Time-Series requests when the
date range is relatively small, and so it is recommended to use ICSF if
the number of IDs requested is greater than the number of dates. If the
number of dates is greater than the number of IDs in the request, it is
recommended to use Time-Series.
*Note: This is a general rule of thumb and performance may vary
depending on the formulas in use.*
tags:
- Cross Sectional
operationId: getCrossSectionalData
parameters:
- $ref: '#/components/parameters/ids'
- $ref: '#/components/parameters/symbolType'
- $ref: '#/components/parameters/universe'
- $ref: '#/components/parameters/universeType_cross_sectional'
- $ref: '#/components/parameters/formulas_cross_sectional'
- $ref: '#/components/parameters/backTestDate'
- $ref: '#/components/parameters/calendar_cross_sectional'
- $ref: '#/components/parameters/fsymId_cross_sectional'
- $ref: '#/components/parameters/displayName_cross_sectional'
- $ref: '#/components/parameters/flatten_cross_sectional'
- $ref: '#/components/parameters/batch'
- $ref: '#/components/parameters/startDate'
- $ref: '#/components/parameters/endDate'
- $ref: '#/components/parameters/frequency'
responses:
'200':
description: >-
Gets an array of `Response Objects` for a list of IDs and Screening
formulas.
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$ref: '#/components/headers/api-supported-versions'
api-deprecated-versions:
$ref: '#/components/headers/api-deprecated-versions'
chain-id:
$ref: '#/components/headers/chain-id'
X-RateLimit-Limit-second:
$ref: '#/components/headers/X-RateLimit-Limit-second'
X-RateLimit-Remaining-second:
$ref: '#/components/headers/X-RateLimit-Remaining-second'
X-RateLimit-Limit-day:
$ref: '#/components/headers/X-RateLimit-Limit-day'
X-RateLimit-Remaining-day:
$ref: '#/components/headers/X-RateLimit-Remaining-day'
content:
application/json:
schema:
$ref: '#/components/schemas/cross_sectional_response'
examples:
Single Equity Id and Single Equity Data Item:
$ref: '#/components/examples/cross-sectional-singleId-singleItem'
Single Equity Id and Single Equity Data Item with fsymId=Y:
$ref: >-
#/components/examples/cross-sectional-singleId-singleItem-fsymId
Multiple Equity Ids and Multiple Equity Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleItem
Multiple Equity Ids and Multiple Equity Data Items with flatten=Y:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleItem-flatten
Multiple Equity Ids and Multiple Calculated Equity Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleCalculatedItem
Multiple Fixed Income Ids and Multiple Fixed Income Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleFixedIncomeId-multipleItem
Small Equity Universe and Single Equity Data Item:
$ref: '#/components/examples/cross-sectional-smallUniv-singleItem'
Debt Universe and Multiple Debt Data Items:
$ref: '#/components/examples/cross-sectional-debtUniv-multipleItem'
Single ID and Multiple dates using ICSF with flatten = N:
$ref: >-
#/components/examples/cross-sectional-ICSF-singleItem-nonflatten
Multiple IDs and Multiple dates using ICSF with flatten = Y:
$ref: >-
#/components/examples/cross-sectional-ICSF-multipleItem-Flatten
'202':
description: Batch request has been accepted.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Request Accepted:
$ref: '#/components/examples/BatchStatusAcceptedResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'405':
$ref: '#/components/responses/405'
'406':
$ref: '#/components/responses/406'
'408':
$ref: '#/components/responses/408'
'415':
$ref: '#/components/responses/415'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
post:
summary: >-
Factset Retrieve data items (Screening formulas) for a list of identifiers or defined universe.
description: >
The `/cross-sectional` endpoint is closely aligned with FactSet’s
powerful data retrieval **Screening language** which is optimized for
analysis of data items at single point in time for different entities
and is extremely efficient for large universes.
The `/cross-sectional` endpoint supports Long Running asynchronous
requests up to **10 minutes** via the `batch` parameter. *This feature
is available to Individual Users subscribed to the Performance Package
and Performance Package Plus Performance Tiers and all Production Users.
If you are unsure which Performance Tier you are subscribed to or you
would like to gain access to the batch capabilities, please contact your
FactSet Account Team or "Report Issue" above and our support teams can
assist.*
***
### Iterated Cross-Sectional Functionality
This endpoint supports the ability to automatically iterate through
different cross sections over time. The **Iterated Cross-Sectional
Functionality (ICSF)** expands the Cross-Sectional endpoint to support
retrieving data items for *multiple dates*, allowing users to take
advantage of the Screening engine’s efficiency even when history is
required.
Use the parameters `startDate`, `endDate`, and `frequency` in the
Cross-Sectional endpoint to provide your desired dates. Specify “0” in
date argument of the Screening formulas provided in the formulas
parameter and/or the universe parameter. Lastly, the Iterated
Cross-Sectional Functionality is required to run as a `batch` request.
Therefore, the batch parameter must be set to “Y”.
Access to backtesting and batch functionality is required to leverage
the Iterated Cross-Sectional Functionality.
**When to use ICSF:**
The ICSF can offer better performance than Time-Series requests when the
date range is relatively small, and so it is recommended to use ICSF if
the number of IDs requested is greater than the number of dates. If the
number of dates is greater than the number of IDs in the request, it is
recommended to use Time-Series.
*Note: This is a general rule of thumb and performance may vary
depending on the formulas in use.*
tags:
- Cross Sectional
operationId: getCrossSectionalDataForList
responses:
'200':
description: >-
Gets an array of `Response Objects` for a list of IDs and Screening
formulas.
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$ref: '#/components/headers/api-supported-versions'
api-deprecated-versions:
$ref: '#/components/headers/api-deprecated-versions'
chain-id:
$ref: '#/components/headers/chain-id'
X-RateLimit-Limit-second:
$ref: '#/components/headers/X-RateLimit-Limit-second'
X-RateLimit-Remaining-second:
$ref: '#/components/headers/X-RateLimit-Remaining-second'
X-RateLimit-Limit-day:
$ref: '#/components/headers/X-RateLimit-Limit-day'
X-RateLimit-Remaining-day:
$ref: '#/components/headers/X-RateLimit-Remaining-day'
content:
application/json:
schema:
$ref: '#/components/schemas/cross_sectional_response'
examples:
Single Equity Id and Single Equity Data Item:
$ref: '#/components/examples/cross-sectional-singleId-singleItem'
Single Equity Id and Single Equity Data Item with fsymId=Y:
$ref: >-
#/components/examples/cross-sectional-singleId-singleItem-fsymId
Multiple Equity Ids and Multiple Equity Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleItem
Multiple Equity Ids and Multiple Equity Data Items with flatten=Y:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleItem-flatten
Multiple Equity Ids and Multiple Calculated Equity Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleId-multipleCalculatedItem
Multiple Fixed Income Ids and Multiple Fixed Income Data Items:
$ref: >-
#/components/examples/cross-sectional-multipleFixedIncomeId-multipleItem
Small Equity Universe and Single Equity Data Item:
$ref: '#/components/examples/cross-sectional-smallUniv-singleItem'
Debt Universe and Multiple Debt Data Items:
$ref: '#/components/examples/cross-sectional-debtUniv-multipleItem'
Single ID and Multiple dates using ICSF with flatten = N:
$ref: >-
#/components/examples/cross-sectional-ICSF-singleItem-nonflatten
Multiple IDs and Multiple dates using ICSF with flatten = Y:
$ref: >-
#/components/examples/cross-sectional-ICSF-multipleItem-Flatten
'202':
description: Batch request has been accepted.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Request Accepted:
$ref: '#/components/examples/BatchStatusAcceptedResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'405':
$ref: '#/components/responses/405'
'406':
$ref: '#/components/responses/406'
'408':
$ref: '#/components/responses/408'
'415':
$ref: '#/components/responses/415'
'429':
$ref: '#/components/responses/429'
'500':
$ref: '#/components/responses/500'
'501':
$ref: '#/components/responses/501'
'503':
$ref: '#/components/responses/503'
requestBody:
$ref: '#/components/requestBodies/cross-sectional-postBody'
/v1/batch-status:
get:
summary: Factset Returns the status for a Batch Request
description: >
Return the status for the underlying batch request that is specified by
the id.
The Formula API supports Long Running asynchronous requests up to **20 minutes** via the `batch` parameter in the `/time-series` endpoint and up to **10 minutes** in the `/cross-sectional` endpoint.
*This feature is available to Individual Users subscribed to the Performance Package and Performance Package Plus Performance Tiers and all Production Users. If you are unsure which Performance Tier you are subscribed to or you would like to gain access to the batch capabilities, please contact your FactSet Account Team or "Report Issue" above and our support teams can assist.*
tags:
- Batch Status
operationId: getBatchStatus
parameters:
- $ref: '#/components/parameters/batchId'
responses:
'201':
description: Batch Request has been completed and the response has been created.
headers:
Location:
description: Path to Batch Request result.
schema:
type: string
example: batch/v1/result?id=2df43e85-ea0f-45c6-bf4a-2baf4d1eaa3c
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Status Done:
$ref: '#/components/examples/BatchStatusDoneResponse'
'202':
description: Batch Request has not finished and the result has NOT been created.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Status Queued:
$ref: '#/components/examples/BatchStatusQueuedResponse'
Batch Status Executing:
$ref: '#/components/examples/BatchStatusExecutingResponse'
Batch Status Failed - Timeout:
$ref: '#/components/examples/BatchStatusFailedResponseTimeout'
Batch Status Failed - Memory Limit:
$ref: '#/components/examples/BatchStatusFailedResponseMemoryLimit'
Batch Status Failed - Other:
$ref: '#/components/examples/BatchStatusFailedResponseOther'
'404':
description: Not Found
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$ref: '#/components/headers/api-supported-versions'
api-deprecated-versions:
$ref: '#/components/headers/api-deprecated-versions'
chain-id:
$ref: '#/components/headers/chain-id'
content:
application/json:
schema:
$ref: '#/components/schemas/error_detail'
example:
id: 5EFCCA8940CAEB6E
code: batchRequestNotFound
title: The Batch Request was not found. It has probably expired.
timeStamp: '2019-11-01 11:09:41.918'
deprecated: false
post:
summary: Factset Returns the status for a Batch Request
description: >
Return the status for the underlying batch request that is specified by
the id.
The Formula API supports Long Running asynchronous requests up to **20 minutes** via the `batch` parameter in the `/time-series` endpoint and up to **10 minutes** in the `/cross-sectional` endpoint.
*This feature is available to Individual Users subscribed to the Performance Package and Performance Package Plus Performance Tiers and all Production Users. If you are unsure which Performance Tier you are subscribed to or you would like to gain access to the batch capabilities, please contact your FactSet Account Team or "Report Issue" above and our support teams can assist.*
tags:
- Batch Status
operationId: getBatchStatusWithPost
responses:
'201':
description: Batch Request has been completed and the response has been created.
headers:
Location:
description: Path to Batch Request result.
schema:
type: string
example: batch/v1/result?id=2df43e85-ea0f-45c6-bf4a-2baf4d1eaa3c
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Status Done:
$ref: '#/components/examples/BatchStatusDoneResponse'
'202':
description: Batch Request has not finished and the result has NOT been created.
content:
application/json:
schema:
$ref: '#/components/schemas/BatchStatusResponse'
examples:
Batch Status Queued:
$ref: '#/components/examples/BatchStatusQueuedResponse'
Batch Status Executing:
$ref: '#/components/examples/BatchStatusExecutingResponse'
Batch Status Failed - Timeout:
$ref: '#/components/examples/BatchStatusFailedResponseTimeout'
Batch Status Failed - Memory Limit:
$ref: '#/components/examples/BatchStatusFailedResponseMemoryLimit'
Batch Status Failed - Other:
$ref: '#/components/examples/BatchStatusFailedResponseOther'
'404':
description: Not Found
headers:
api-version:
$ref: '#/components/headers/api-version'
api-supported-versions:
$r
# --- truncated at 32 KB (178 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/factset/refs/heads/main/openapi/formula-openapi-original.yml