Introducing the Fundamental Web Service

Fundamental Software announces the launch of the Fundamental Web Service – a secure, centralised RESTful API entry point to the Fundamental Portfolio Manager (FPM), hosted on the same highly available, scalable SaaS infrastructure as the core FPM solution.

The Fundamental Web Service extends the existing mechanisms in the traditional FPM UI for imports and data extraction. By routing all activity through FPM Server, the same business rules, accounting checks, data validations and authorisation model apply consistently across both user-driven and system-driven interfaces.

Simple API, Rich Behaviour

A central design principle is a simple, stable API schema that leverages the mature capabilities already present in FPM:

• Consistent behaviour across channels
The Web Service uses FPM Server as the execution engine, ensuring identical processing, posting and control frameworks as the traditional UI.
• Powerful export capabilities via custom reporting
The Web Service extends FPM’s custom reporting framework to deliver highly targeted exports that return only the required data and nothing more. This reduces payload size, simplifies downstream processing and limits exposure of unnecessary information.
• Stable schema, flexible functionality
Because the Web Service sits on top of FPM’s existing import, export and reporting infrastructure, API contracts remain stable even as new portfolios, instruments and business features are added within FPM. Functional changes are primarily handled through configuration and reporting definitions rather than frequent API redesign.

Modernising Beyond SFTP

Many existing integrations rely on flat file exchanges over SFTP. This pattern has been effective, but it carries operational drawbacks: static folders per customer, manual credential and key rotation, limited context on processing outcomes, and support interventions when batches are late or files deviate from expected formats.

The Fundamental Web Service provides a modern replacement for new and future integrations, addressing these issues with an API-based model that is more observable, more secure, easier to automate and simpler to support.

SFTP will remain an important capability within the FPM ecosystem, and existing SFTP-based processes will continue running as currently configured. Strategically, however, the preferred integration model is clear: API over SFTP, delivering a cleaner, more controlled and more maintainable interaction surface for systems integrating with FPM.