Choosing an integration approach
TreasurySpring can be reached in several different ways. The right one depends on what you're trying to do, what systems your team already operates, and how much engineering time you'd like to invest. This page is a decision aid — find the row that best matches your situation and follow the links from there.
| Approach | Best for | Setup effort | What you get |
|---|---|---|---|
| REST API | Building a custom integration into your TMS, internal portal, or back-office. Full control over what you call and when. | Days to weeks | Real-time read and subscription placement, full schema control. |
| MCP (AI agent) | Ad-hoc queries from Claude, Cursor, Copilot, and similar tools. "What are my GBP holdings maturing this quarter?" without writing code. | Minutes | Conversational read-only access; the agent infers, and you verify. |
| TMS connector | Systems that are already integrated with TreasurySpring. The current list is available at app.treasuryspring.com/portal/integrations. | Coordination with your TMS vendor and TreasurySpring | Position feed and reconciliation inside your existing TMS workflow. |
| File-based delivery | Back-office pipelines built around scheduled file feeds. Available on request — please contact your relationship manager. | Set up with your relationship manager | Daily file delivery on a schedule that suits your back-office. |
| Portal Excel export | One-off downloads, reconciliation spreadsheets, ad-hoc reporting. | Log in to the portal, open the Portfolio page, and use the Export button. | Excel files, on demand. |
When to use REST
The REST API is a good fit when you need:
- Programmatic subscription placement (currently available through REST or the portal).
- Real-time event reconciliation — webhook-style feeds via cursor pagination.
- Custom UI surfaces (for example, embedding holdings or available indications inside your own treasury dashboard).
- Multi-entity orchestration with per-entity audit trails.
A good place to begin is the Quickstart → Authentication → Identifiers.
When to use MCP
MCP tends to suit cases where:
- The person making the query is the user (a treasurer, a portfolio analyst).
- The output goes into a chat, an email, a Notion page, or a Slack reply — rather than a system of record.
- Minimal infrastructure is preferred: install a connector, sign in, ask questions.
It is read-only today. Anything that would mutate state — placing a subscription, changing a maturity action — needs to go through the REST API or the portal.
See the MCP guide for the full setup.
When to use a TMS connector
If your treasury platform already supports TreasurySpring through a connector module, this is usually the lightest path. The current list of supported integrations is maintained at app.treasuryspring.com/portal/integrations; your TreasurySpring account manager can confirm which connector versions are in production and which are still in development.
If your TMS isn't listed yet, you can request a new integration from the same page. We'll coordinate with the vendor on availability and timing.
TMS connectors typically expose a subset of the REST API's surface — enough for position feeds and reconciliation, though some workflows may still need direct REST calls.
When to use file-based delivery
For back-offices built around scheduled daily file feeds, TreasurySpring can deliver position files via SFTP. This tends to be a good fit for:
- Large enterprise teams whose existing pipeline is built around files in and files out.
- Compliance environments where real-time API access is restricted.
- Use cases where T+1 timing is acceptable.
SFTP delivery is set up on a per-customer basis. If this is something you'd like to explore, please contact your relationship manager so we can scope the configuration with you. You can also request a new integration through app.treasuryspring.com/portal/integrations.
When to use the portal export
For one-off needs (a quarterly reconciliation, a board pack, an audit pull), the portal's Excel export is often the quickest option. Log in to the portal, open the Portfolio page, and use the Export button to download the current view as an Excel file.
If you find yourself exporting the same view repeatedly, the REST API or MCP may be a better long-term fit.
Can I mix approaches?
Yes. Most production integrations combine more than one approach. Common combinations include:
- REST for writes and MCP for reads — the engineering team builds the subscription-placement integration in REST, while the treasury team uses MCP for daily monitoring questions.
- TMS connector for daily reconciliation and REST for anything the connector doesn't cover.
- File-based delivery for compliance reports and REST for live workflow.
The credentials and permission model are shared across all approaches — granting a user access in the portal grants them access across REST, MCP, and (where applicable) the TMS connectors.