Closing out 2023 with our last API Release! We are super excited to share with you all some changes to the platform. If you have any questions about this release feel free to reach out to us on the slack channels or send us an email at: [email protected].

🚀 New Features

Nothing new but we are working on some big things for the new year! Have a great holiday season and a happy new year. See you in 2024!

🎉 Feature Enhancements

Accounts

Performance
We are back with some account performance changes that will allow you to fetch performance information from accounts that are in a FROZEN status. Additionally, the API will allow you to fetch performance information from accounts that have been closed tailing 90 days after the closure date.

Account Details
We are introducing new fields and enhancing fields on the Accounts API.

The pattern day trade Restricted (pdtRestricted) is specifically when the account is restricted due to pattern day trading. The good faith violation (gfvRestricted) is when the account is restricted due to not paying for securities when funds are in flight. Pattern day trader is when an account/user is identified as a pattern day trader.

Additionally, we are adding the “beginning of day buying power” (bodDTBP) calculation to the Accounts API. This calculation is what is the buying power of the customer at the start of the trading day.

This enhancement can also be viewed in DriveHub by searching the account, clicking into details, and then just below equity, a new “BOD DTBP” field will appear.

To ensure this feature is activated, contact your account manager.

Orders

Order events are getting better. We are happy to announce that SEC and TAF fees will now be included inside the fee calculation on orders.completed. To learn more about order events, see here.

ACATS

We are adding a new field called acatTransit on the listing and fetching of ACATS. The new field will identify if the ACAT is to a DriveWealth account (ACAT_IN) or if the ACAT is to a non-DriveWealth account (ACAT_OUT).

👠🐛 Squashing Bugs

User

We are out here squashing bugs so you all can have a better experience. There was an issue where risk-tolerance accepted an enum value and would return the string non-enum representation of this value. We have fixed that to now return ENUM on the fetch.

To see this update, check out our documentation.

🪵 ChangeLog

## Modified endpoints

**`GET /accounts/{accountID}`**

* Modified the `200` response:
    * Changed object property `account`
        * Added property `gfvRestricted`
        * Added property `patternDayTrader`
        * Added property `pdtRestricted`

**`PATCH /accounts/{accountID}`**

* Modified the `200` response:
    * Modified the schema option `AccountDetailRes`
        * Changed object property `account`
            * Added property `gfvRestricted`
            * Added property `patternDayTrader`
            * Added property `pdtRestricted`

**`GET /accounts/{accountID}/summary`**

* Modified the `200` response:
    * Changed object property `margin`
        * Added property `bodDTBP`

**`GET /accounts/{accountID}/summary/margin`**

* Modified the `200` response:
    * Changed object property `margin`
        * Added property `bodDTBP`

**`GET /asset-transfers`**

* Modified the `200` response:
    * Changed array property `data`

**`POST /asset-transfers/acats`**

* Modified the `200` response:
    * Added property `acatTransit`

**`POST /asset-transfers/minor-graduation`**

* Modified the `200` response:
    * Added property `acatTransit`

**`GET /asset-transfers/{assetTransferID}`**

* Modified the `200` response:
    * Added property `acatTransit`