Skip to content

FTS Apollo APIs

Apollo offers a rich set of functionality as a web application. This is great for many use-cases, but some users may desire programmatic or machine-readable access to FTS Apollo™ capabilities. For these users, REST API access is a great option.

API Access

API access is not enabled by default. To get access to APIs, please contact your account manager or sales representative.

When to use an API vs Widget

If your use-case requires a specific subset of FTS Apollo™ data or functionality, then using the API might be right for you. Here are some common scenarios where API access makes sense versus a widget:

Category Scenario Best Choice
Display Integrate data or analytics within an application, with basic color, logo, and font matching. Widget
Display Integrate data or analytics within an application, with deeply integrated stylesheets and formatting. API
Consumer End users will be the consumer of data. Widget
Consumer Automated systems will be the consumer of data. API
Technical Experience Basic technical understanding. Widget
Technical Experience Knowledge of programming or scripting. API
Interactivity A self-contained set of functionality that does not need to drive workflows. Widget
Interactivity Data interactions need to be captured and acted upon. For example, clicking the title of a document. API

API Completeness

The FTS Apollo™ API contains every endpoint and function needed to interface with FTS Apollo™ data in a programmatic way. In fact, the FTS Apollo™ web application itself uses the same API that direct API consumers use! Below is a diagram showing how different methods of access.

High-level API overview diagram

As you can see, since the FTS Apollo™ application uses the same API as direct consumers, anything available in the web app is programmatically accessible via the API.

API Help


Help Home FTS Apollo™ Help RegLens® Help

Last update: March 9, 2022
Back to top