Welcome to the WealthTech API developer hub from Bridge Financial Technology. Here we provide comprehensive guides, APIs reference documentation, requests examples and all supporting information to successfully build a modern financial apps and integration with BridgeFT.

What is the WealthTech API?

BridgeFT WealthTech API is the industry’s only API-first, wealth infrastructure framework that delivers critical data and application needs to build next generation wealth management applications. Offering a single connection via a modern API, the WealthTech API offers full access to trade-ready, multi-custodial data sources and rich wealth applications that enable clients to accelerate their time to market, reduce technology overhead and costs, and deliver highly differentiated solutions to drive growth.

What can you find here?

The Documentation section provides high level overviews of the platform functionality and processes, as well as guides and API implementation details. We cover best practices, authentication and more.

Our API Reference contains a comprehensive and detailed inventory of all our API endpoints including expected inputs, responses, supported HTTP methods and possible error codes.

To help you jump start and accelerate your development, we've created some Recipes outlining the most common use cases along with examples for how to best utilize our APIs to implement them.

Finally, make sure to regularly check the Changelog to stay up to date with new features, updates and releases.

Base URL

WealthTech API base URL: https://api.bridgeft.com/v2

Best Practices and Recommendations

WealthTech API doesn't impose any rate limits at the moment, however we may deny requests from a particular user or API key if we identify abuse or generally unacceptable consumption of data. Below are some best practices you should implement when integrating with the WealthTech API:

Don't invoke the API from your test suite; instead, mock responses coming back from the API.
Implement retry behavior with exponential backoff to account for failures due to network latency or other reasons.
Consume and log error messages, codes and eventID values in your logs so you can better assist our development team in identifying any issues you may encounter either during development or in production.
Generally use the default pagination limit. WealthTech API can push large payloads of data out; make sure you're able to handle the data I/O when increasing the pagination size. We also strongly recommend to use pagination in any calls where applicable. Please refer to this: Pagination page for implementation details.
We recommend filtering data unless you're executing a system-wide synchronization. Some of our APIs require filters to be applied, in that case you may see them highlighted in red in the list if query parameters. For example check out the reference for Realized Gain and Losses API where you can see reported_date is a required parameter. Also check out documentation about Filtering implementation for more details.
Be mindful of the number of requests you make. We recommend synchronous invocation to avoid flooding our API and receiving a 429 error message as a result.

Developer Support

If you run into trouble or have any questions regarding WealthTech API and your application integration feel free to submit your request in our BridgeFT API Support Portal. For any issues with accessing the BridgeFT API Support Portal, please reach out to your BridgeFT Account Manager.