FactSet APIConnect FactSet without building on its API
FactSet has a REST API. FactSet clients only: you sign in to the Developer Portal with a corporate email and need a FactSet username-serial account, and the account team handles access (the exact subscription terms are not published). If you're reading the docs because you need FactSet to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across FactSet and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessFactSet clients only
What the FactSet API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (recommended) or API key (HTTP Basic with FactSet username-serial + API key)
- Who can get access
- FactSet clients only: you sign in to the Developer Portal with a corporate email and need a FactSet username-serial account, and the account team handles access (the exact subscription terms are not published).
- What it covers
- Financial content and analytics APIs such as prices, fundamentals, estimates, ownership, documents, portfolio analytics engines (e.g., SPAR), and trading.
Official docs: developer.factset.com. Checked September 2026. Vendors change access terms, so confirm with FactSet before you build.
Building on the FactSet API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get FactSet credentials, and manage tokens and refreshes. | Connect your FactSet account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the FactSet task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting FactSet work off someone's desk, the build is the slow part.
What teams usually want the FactSet API for
Build a data-backed report
Caddi pulls FactSet data into a formatted Excel report on schedule.
Sync data to the CRM
Caddi carries FactSet figures into client records without manual entry.
Distribute the output
Caddi compiles FactSet-sourced data and sends it to the team automatically.
FactSet API questions
Does FactSet have an API?
Yes. FactSet has a REST API, authenticated with OAuth 2.0 (recommended) or API key (HTTP Basic with FactSet username-serial + API key). The official documentation is at https://developer.factset.com/.
How do I get access to the FactSet API?
FactSet clients only: you sign in to the Developer Portal with a corporate email and need a FactSet username-serial account, and the account team handles access (the exact subscription terms are not published).
Can I connect FactSet to my other tools without writing code against its API?
Yes. With Caddi you show the FactSet task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across FactSet and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate FactSet with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for FactSet is reviewed before it runs in production, and every run is logged.
Connect FactSet without the build.
Drop your work email and pick a time. We'll show you Caddi running your FactSet workflow end to end.