How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Factset Historical API

The Historical API from Factset — 4 operation(s) for historical.

Factset Historical API is one of 460 APIs that Factset publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Historical. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, code examples, a changelog, and 1 JSON Schema.

This API exposes 5 operations across 4 paths, and defines 19 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://api.factset.com, https://api-sandbox.factset.com.

5 operations 4 paths 19 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.factset.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Factset Historical API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Historical 5
GET
/streetaccount/historical/request-files
Factset Returns the Jobid
2 params → 200400401403500
GET
/streetaccount/historical/check-status
Factset Returns the Status and Percentage of Completion for the Requested Jobid
3 params → 200400401403500
GET
/streetaccount/historical/get-files
Factset Returns the Streetaccount Xml Files for the Specified Date Range
3 params → 200400401403500
GET
/symbology/v3/historical-identifier-resolution
Factset Returns the Specified Historical Output Identifiers for the Given Input Identifier.
historicalIdentifierResolution 4 params → 200400401403415500
POST
/symbology/v3/historical-identifier-resolution
Factset Returns the Specified Historical Output Identifiers for the Given Input Identifier.
batchHistoricalIdentifierResolution body → 200400401403415500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are identifierResolutionHistorical (9 properties), getfiles (7 properties), checkstatus (7 properties), errorObject (4 properties). Each schema is shown below with its type and property counts.

errorResponseHistorical
object
Error Default Response
1 property
requestfilesResponse
object
2 properties
identifierResolutionHistoricalResponse
object
Response object for Historical Identifier Resolution endpoint.
1 property
checkstatusResponse
object
2 properties
getfiles
object
7 properties
getAsOfDate
string
As of date for historical symbol request in YYYY-MM-DD format. If no asOfDate is requested, the response will include the full history of the identifier.
checkstatus
object
7 properties
identifierResolutionHistoricalRequest
object
Request object for Historical Identifier Resolution endpoint.
1 property 1 required
identifierResolutionHistoricalRequestBody
object
Request object for Historical Identifier Resolution endpoint.
4 properties 3 required
paginationOne
object
List of pagination objects
4 properties
isPartialOne
object
If the value is true, it indicates additional results are available. False represents that this is the last set of results for this request.
1 property
getHistoricalOutputSymbolTypes
array
Requested identifiers to be returned. Multiple identifier types can be requested with each request.
errorObject
object
4 properties
getfilesResponse
object
2 properties
getIdsResolution
array
Requested market securities or entities. All requested identifiers must be of the same type. Accepted identifiers include all FactSet Permanent Identifiers typ…
metaOne
object
Array of metadata objects
2 properties
identifierResolutionHistorical
object
Historical Identifier Resolution data object.
9 properties
getHistoricalInputSymbolType
string
The type of symbol submitted for resolution to other identifiers. Only one type of symbol is accepted with each request.
StreetAccountStatus
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

factset-historical-api-openapi.yml Raw ↑

Other APIs Factset publishes across the network.

FactSet Recommendation List API for Digital Portals
FactSet Bonds API for Digital Portals
FactSet Virtual Portfolio API for Digital Portals
FactSet Stocks API for Digital Portals
FactSet Securitized Derivatives API for Digital Portals
FactSet Watchlist API for Digital Portals
FactSet Funds API for Digital Portals
FactSet Data Monitor API
FactSet Mergers and Acquisitions API
FactSet News API
News API for Digital Portals
FactSet Real-Time Options API
Where this information came from

This is an independent, third-party profile of Factset Historical API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.