FactSet: enterprise data, Portware execution technology, digital APIs and implementation scope

FactSet supplies financial data, analytical applications, digital-portal capabilities and institutional execution technology. For a brokerage, those can support research, customer information, internal workflows or a trading desk, but they are different purchases. Portware is the execution-management product within the wider FactSet offering.[1][2]

A useful procurement decision starts with the intended user and decision. A broker’s customer portal, research team and execution desk may all need data, but they require different latency, entitlement, workflow and retention arrangements. Buying a workstation should not be assumed to include the rights or technology for a public redistribution service.

FactSet’s developer recipe for StreetAccount uses company identifiers to request relevant news and populate an internal CRM or portal. It recommends OAuth 2.0 while also describing API-key support. The recipe specifically identifies company-name mapping as a commercial item to discuss with the account team. This is more precise than treating every API as an interchangeable URL.[5]

The 2022 Aladdin partnership announcement described integration of Portware EMS capabilities through APIs. A later 2025 announcement described availability of IntelligentCross JumpStart inside Portware with Jefferies low-touch access. These are specific dated connections, not a claim that every venue, broker or liquidity pool is available to every subscriber.[3][1]

A broker integrating multiple content sets should reconcile security identifiers, currency, units, adjustment basis and event time before combining them. A valid API response can still be inappropriate for the intended calculation. Batch jobs should also distinguish an empty result, an entitlement failure, a rate limit and a genuinely missing observation.

A complete current cash tariff for the relevant institutional configuration was not publicly established. The appropriate commercial request is therefore product- and use-specific. FactSet’s developer material explicitly directs buyers to an account team for some setup and mapping costs rather than publishing a universal charge.[5]

Compare recurring content charges, application charges and one-time implementation costs separately. Include exchange fees, professional-user classifications, display versus non-display usage and any onward distribution. These are procurement questions, not claims that each item is charged in every contract.

The tick-history recipe requires the buyer’s cloud provider, Snowflake region, account and instrument specifications. Its stated tutorial time is not an enterprise implementation deadline. Entitlements, data quality checks and downstream storage design remain part of a production project.[4]

IRN’s separate sandbox supports testing away from the customer’s existing research database. That distinction is consequential for write-enabled tools: a configuration or contact change sent to production may affect a real shared workflow. Use an authorised test environment and establish a rollback procedure before enabling automated updates.[8]

For a new portal, test the exact externally displayed fields and identifier mapping. A company’s primary listing, a local notation and the legal entity can be different objects. The application should preserve that distinction through quote displays, instrument search and news filtering rather than silently merging records because names look similar.

FactSet publishes general consulting assistance around the clock and separate support contacts for specialty products. Trading/Portware, Digital Solutions and general content enquiries therefore need not use the same queue. The advertised support availability does not establish a contract-specific resolution target.[11]

The developer support workflow asks for the response request key when available and expressly says not to include passwords or API keys. Retaining that request identifier, the endpoint and a redacted example response can make an investigation reproducible without exposing credentials.[12]

The digital-portal derivatives documentation explicitly requires appropriate application permissions for identifiers and data. Technical authentication is not the whole entitlement model. A broker must also obtain the content and usage rights for the chosen application and audience.[6]

FactSet’s public legal page governs its website and public services; it should not be mistaken for the complete negotiated enterprise data agreement. Its existence does not settle an institutional customer’s redistribution, AI-training, retention or derived-data rights. Those rights need to be established in the relevant product contract.[13]

Execution-management technology also does not confer brokerage, custody or clearing permissions. A connection through Portware must be matched to the customer’s actual broker and venue relationships. A dataset describing an instrument or an indicative bond price is not a commitment to execute a trade at that value.

FactSet Research Systems Inc. completed its acquisition of Portware in October 2015. Current FactSet product and support material continues to present Portware as part of its trading offering.[2][11]

The September 2025 MarketAxess announcement illustrates the distinction between content and delivery: CP+ data was made available in FactSet Workstation and real-time feeds. A buyer should identify the specific entitlement and use case rather than assume that every FactSet licence includes that content.[14]

Operator

FactSet Research Systems Inc. and the relevant contracting affiliate

Service scope

FactSet supplies financial data, analytics, portal APIs and Portware execution technology. This profile explains their different commercial and technical scopes, current developer interfaces, support routes and data-permission boundaries.

Customer types

Institutional brokers and trading desks; Banks, asset managers and wealth firms; Financial application and data teams

Delivery

Hosted; API; Managed service; Hybrid

Pricing publication

Quote only

Platforms

FactSet Workstation; Portware; Digital Portal APIs; IRN APIs

Implementation

Product-specific entitlement, identifier mapping, data delivery and application integration; development and production access must be separated.

Support

General consulting support and separate specialty routes for Portware and Digital Solutions; authenticated API issue reporting.

Permissions and regulatory scope

Information and technology profile. Authentication does not confer all content/redistribution rights or financial-service permissions.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12Source 13Source 14

Knowledge Services MCP lists entity and date resolution tools with a July 2026 initial-release entry. It helps turn a natural-language request into the structured identifiers expected by other services. That improves the mechanics of retrieval but does not eliminate the need to check that the requested entity, period and field match the user’s question.[9]

The Conversational API documentation labels version 0 as beta and describes streamed chat-completion responses. An integration should retain that status distinction rather than present every experimental endpoint as a mature replacement for established data retrieval.[10]

A vendor-exit plan should distinguish the broker’s own research content from licensed external datasets and software. Exportability, post-termination storage, deletion and continuing display rights may differ. Record those obligations when signing, not after a portal depends on a feed that can no longer be displayed.