Changelog
Back to All

July 17 2025 - v.2025.1.0

25 days ago by Mitchell Jones

To Our Valued BridgeFT Client we're excited to wrap up Q2 by sharing important product updates, data feed expansions, and bug fixes to further enhance the BridgeFT client experience.
...Click here to view more updates...

🆕 Margin Account Indicator

We’ve added a Margin Account Indicator to the Accounts API to help users quickly identify accounts that are margin-enabled. This simple yet powerful field adds a new layer of visibility into account capabilities, supporting smarter decision-making and streamlined compliance checks.

🔍 How It Works

The new field flags whether an account is authorized for margin trading. This allows platforms and operations teams to filter, segment, or validate accounts based on trading permissions with ease.

📡 Supported Sources:

  • SWB (Schwab)
  • NFS (Fidelity)
  • PER (Pershing)
  • IBK (Interactive Brokers)

With this update, users can enhance trading workflows, improve risk monitoring, and gain a more complete picture of account characteristics—all within the existing Accounts API.

For more information about the new Margin Account Indicator (source_margin_indicator), please visit our API Reference Page and our Margin Indicator Definitions on the BridgeFT API Data Dictionary Page for more details.

🛠️ Pontera Data Feed (General Availability July 25th)

BridgeFT has added Pontera to its list of data feeds. Through this partnership, our clients will now be able to seamlessly manage clients' 401(k), 403(b), and other held-away accounts alongside our other multi-custodial data sources. Reach out to your Account Manager or Relationship Manager to learn how you can get setup with the Pontera Data Feed.

🛠️ Pershing and Apex Data Migration to New Ingestion Pipeline

We are migrating Pershing and Apex data to our new ingestion pipeline, enabling faster processing and improved data delivery. This upgrade enhances our ability to provide Pershing and Apex data with:

  • Increased processing speed
  • Improved accuracy and availability
  • A more sustainable and reliable data source

By leveraging this new pipeline for Atlas and the WealthTech API, we ensure more efficient and consistent data delivery, allowing us to better support your needs.

🔌New Delete Household Endpoint Added

Clients can now delete a household by specifying its household ID in the request parameter, streamlining household data management and aligning with other deletion operations. Consult our API Reference for more details.

🧰Fixes & Improvements

We’ve added a few new values to the Account Type and Account Name fields across BridgeFT services. These additions improve the clarity and usefulness of account data, helping users better understand and classify accounts in downstream workflows.

We’ve optimized key endpoints across BridgeFT services, resulting in faster response times and improved overall performance. Enjoy a quicker, more seamless experience when accessing data through our APIs.

We’ve enhanced the processing of Apex transaction data, specifically for sweeps and transfers, to improve reporting accuracy across BridgeFT services. This update ensures more consistent and reliable transaction records, supporting better reconciliation and downstream analysis.

We’ve enhanced the logic for interpreting various codes sent by Fidelity NFS, resulting in more accurate position records. This expanded code reading improves data precision, supporting better portfolio tracking and Account reconciliation.

We have marked the "status" field within the Accounts API as deprecated. This means that the "status" field will either be removed or replaced in a later version of our WealthTech API, however the field will still remain available within the current version of the API. This is not a breaking change and will not have any impact on API users currently using the most recent or past version of the API.