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 Database API

The Database API from Factset — 24 operation(s) for database.

Factset Database 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 Database. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, code examples, a changelog, and 1 JSON Schema.

This API exposes 32 operations across 24 paths, and defines 20 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.

32 operations 24 paths 20 schemas 4 DELETE18 GET6 POST4 PUT

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 Database API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 32

Across 24 paths, the API surfaces 32 operations — 4 DELETE, 18 GET, 6 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Database 32
GET
/factset-prices/v1/database-rollover
Factset Gets the Latest Relative Rollover Date for the Database.
getDatabaseRollover → 200400401403415500
POST
/factset-prices/v1/database-rollover
Factset Gets the Latest Relative Rollover Date for the Database.
getDatabaseRolloverForList → 200400401403415500
GET
/database/jobs/{id}/status
Returns the current status of a long running request. The full URL is normally provided for you in the Location header of a long running response.
getStatus 1 param → 201202400403404406429500
GET
/database/{path}/audit
Returns a list of the most recent "modificationTimes" in long datetime format
getAudit 1 param → 202400403404406429500503
GET
/database/{path}/audit/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceAudit 2 params → 200400403404406429500503
GET
/database/{path}/stats
Returns a summary of OFDB metadata and data points
getStats 1 param → 202400403404406429500503
GET
/database/{path}/stats/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceStats 2 params → 200400403404406429500503
GET
/database/{path}/fields
Returns all the fields in the database(OFDB, OMSOFDB, ECONOFDB)
getFields 1 param → 202400403404406429500503
POST
/database/{path}/fields
Allows users to add fields to existing OFDBs
addFields 1 param body → 202400403404406429500503
GET
/database/{path}/fields/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceFields 2 params → 200400403404406429500503
POST
/database/{path}/delete
Allows users to delete various combinations of symbols, dates, and fields from the desired OFDB
deleteBulkItems 1 param body → 202400403404406429500503
GET
/database/{path}/delete/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceBulkDelete 2 params → 200400403404406429500503
GET
/database/{path}/symbols
Returns all the symbols in the database(OFDB, OMSOFDB, ECONOFDB)
getSymbols 6 params → 202400403404406429500503
POST
/database/{path}/symbols
Creates a new symbol with single/multiple dates for 3d database(OFDB). Creates a symbol for 2d database(OFDB)
addSymbols 1 param body → 202400403404406413429500
PUT
/database/{path}/symbols
Updates existing symbols for single/multiple dates or adds a new symbol/date within a symbol if not present in 3d database(OFDB). Updates an existing symbol field value or adds a new symbol if not pr…
updateSymbols 1 param body → 202400403404406413429500
GET
/database/{path}/symbols/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceSymbols 2 params → 200400403404406429500503
PUT
/database/{path}/symbols/{symbol}
Updates an existing symbol field value for single/multiple dates or adds a new symbol/date within a symbol if not present in 3d database(OFDB). Updates an existing symbol field value or adds a new sy…
updateSymbol 2 params body → 202400403404406413429500
DELETE
/database/{path}/symbols/{symbol}
Deletes all data specific to the symbol in both 2d and 3d database(OFDB). This includes all the dates related to that symbols in 3d database(OFDB)
deleteSymbol 2 params → 202204400403404406429500
GET
/database/{path}/symbols/{symbol}/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceSymbol 3 params → 200400403404406429500503
GET
/database/{path}/dates
Returns all the dates in the database(OFDB, OMSOFDB, ECONOFDB)
getDates 6 params → 202400403404406429500503
POST
/database/{path}/dates
Creates a new date with single/multiple symbols for a 3d database(OFDB).
addDates 1 param body → 202400403404406413429500
PUT
/database/{path}/dates
Updates existing dates for single/multiple symbols or adds a new date/symbol within a date if not present in 3d database(OFDB).
updateDates 1 param body → 202400403404406413429500
GET
/database/{path}/dates/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceDates 2 params → 200400403404406429500503
PUT
/database/{path}/dates/{date}
Updates an existing date field value for single/multiple symbols or adds a new date/symbol within a date if not present in 3d database(OFDB).
updateDate 2 params body → 202400403404406413429500
DELETE
/database/{path}/dates/{date}
Deletes all data specific to the date in 3d database(OFDB). This includes all the symbols related to that date
deleteDate 2 params → 202204400403404406429500
GET
/database/{path}/dates/{date}/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceDate 3 params → 200202400403404406429500
DELETE
/database/{path}/dates/{date}/symbols/{symbol}
Deletes data specific to the symbol and date from a 3d database(OFDB).
deleteDateFromSymbol 3 params → 202204400403404406429500
DELETE
/database/{path}/dates/{date}/symbols/{symbol}/jobs/{id}
Deletes data specific to the symbol and date from a 3d database(OFDB).
getResourceDateFromSymbol 4 params → 200204400403404406429500
GET
/database/{path}
Returns the data in the database(OFDB, OMSOFDB, ECONOFDB) for the mentioned Symbol or Date. Atleast one parameter(Symbol/Date) is required. For a range of dates symbol parameter is mandatory.
getData 12 params → 202400403404406429500503
GET
/database/{path}/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceData 2 params → 200400403404406429500503
POST
/database
Creates a 2d or 3d database(OFDB). Users will note that not every field requires all the parameters listed in the schema. Please review FactSet data types on the OA for further guidance.
createDatabase body → 202400403404406429500503
GET
/database/jobs/{id}
Returns the end results of a long running request. The full URL is normally provided for you in the Location header of a finished long running response.
getResourceDatabase 1 param → 200400403404406429500503

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are rollover (6 properties), errorResponse (5 properties), DatabaseSchema (1 property), SuccessPostResponse (1 property). Each schema is shown below with its type and property counts.

AddDates
object
1 property
Symbols
array
UpdateDate
object
Set of fields along with symbol is mandatory to update the date.
1 property
Fields
array
BulkDelete
object
1 property
BulkDeleteArrayItemNested
SuccessPostResponse
object
Response format of any kind of post response
1 property
DatabaseSchema
object
1 property
AddFields
object
1 property
rolloverResponse
object
1 property
errorResponse
object
5 properties
Dates
array
BulkDeleteArrayItem
BulkDeleteArray
array
A list of the various backend responses needed for the bulk delete. These typically contain data points that failed to be deleted, and are in the order of: Del…
UpdateDates
object
Set of fields along with symbol is mandatory to update the date.
1 property
CreateDatabase
object
1 property
UpdateSymbol
object
Any arbitary set of fields that are provided while creating the ofdb and their values.
1 property
UpdateSymbols
object
Any arbitrary set of fields that are provided while creating the ofdb and their values.
1 property
AddSymbols
object
1 property
rollover
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

factset-database-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 Database 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.