New API release including AutoGiro Orders
February 1, 2021. Stefan Willebrand.
Many of our customers use Autogiro to automatically collect cash and send cash to end customers and they also use RecurringOrderTemplates to work with recurring savings. Until now it has been difficult to retrieve the generated AutoGiroOrders to check on the resulting orders but now we have just published this new API method which you can read about here.
In addition we also added a new property to GetTradeOrders where you can now filter on a property called FourEyesStatus and get information about it in the response. FourEyesStatus tells you if the order has been approved by a second person if you have this in your process for order entry.
Finally we added the response property AccountTypeKey to GetPositions. Up until now it has only been possible to filter on this property but in many cases when working with positions in the API you would like to know what account type each order is associated to. Historically the only way to get this information has been to also collect all the accounts by using GetAccounts which introduces unnecessary complexity to this simple requirement.
Happy coding!
More Developer posts
Automating complex corporate actions for stock trading firms - October 6, 2022
How can you automate corporate actions as a distributor of financial instruments? - March 13, 2022
Why I love using Bricknode for new financial applications - January 19, 2022
How to connect to the BFS API using Visual Studio and our NuGet package - October 12, 2021
Working with account balance alerts for back office users in Bricknode Broker - July 16, 2021
How to handle acquisition values for internal transfers via API - February 26, 2021
We are speeding up the release rate of new API functionality - January 24, 2021
Use JSON to work with complex data in custom fields - June 27, 2020
The great new feature called KycDate - February 16, 2020