How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

DriveWealth Portfolios API

The Portfolios API from DriveWealth — 3 operation(s) for portfolios.

DriveWealth Portfolios API is one of 31 APIs that DriveWealth publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Portfolio. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://bo-api.drivewealth.io/back-office, https://bo-api.drivewealth.net/back-office.

4 operations 3 paths 34 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.drivewealth.net
Authentication
HTTP Bearer, API Key, API Key
Resource Areas
1

Authentication & Security 3

DriveWealth Portfolios API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as dw-client-app-key (dwAppKey). An API key is passed in the header as dw-auth-token (sessionToken).

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Portfolios 4
POST
/managed/portfoliosdeprecated
Create Portfolio
body → 200
GET
/managed/portfolios/{portfolioID}deprecated
Retrieve Portfolio
1 param → 200
PATCH
/managed/portfolios/{portfolioID}deprecated
Update Portfolio
1 param body → 200
GET
/users/{userID}/managed/portfoliodeprecated
List Portfolios by Advisor
1 param → 200

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are portfolioRes (9 properties), FundByUserID (8 properties), portfolioResHoldingsObject (8 properties), PortfolioByUserID (7 properties). Each schema is shown below with its type and property counts.

fundDescription
string
A user defined description that describes the underlying fund.
portfolioReq
object
6 properties 6 required
portfolioTriggers
object
An object that holds the details of when to trigger a rebalance of a Portfolio.
5 properties 5 required
fundUpperLowerBound
number
holdingsObject
object
An object in the holdings array that holds the instrumentID and target.
2 properties
portfolioRes
object
9 properties
fundLowerBound
number
portfolioDescription
string
A user defined description that describes the underlying portfolio.
fundMaxAllowed
number
The total drift amount for this instrument.
clientPortfolioID
string
A user defined identifier attached to the portfolio.
portfolioName
string
A user defined name that describes the underlying portfolio.
portfolioMaxAllowed
number
The total drift amount for this fund or cash.
PortfolioByUserID.Triggers
object
5 properties
fundType
string
The type of fund.
portfolioLowerBound
number
FundByUserID.Triggers
object
5 properties
triggerTypes
string
The type of trigger associated to the fund as a whole or an individual instrument.
fundName
string
A user defined name that describes the underlying fund.
PortfolioByUserID
object
7 properties
managedAccountsUserID
string
The unique identifier of the registered investment advisors account.
FundByUserID.Holdings
object
2 properties
FundByUserID
object
8 properties
portfolioReqHoldings
object
3 properties 2 required
fundID
string
The unique identifier of a fund.
userID
string
A unique identifier created for each User on DriveWealth's platform.
fundTarget
number
The individual targeted weight of the instrument.
triggersObject
object
An object that holds the details of when to trigger a rebalance of the Fund.
5 properties 5 required
portfolioUpperLowerBound
number
instrumentID
string
A unique ID created by DriveWealth to identify a specific instrument.
portfolioResHoldingsObject
object
An array of objects that hold details of a Fund in a Portfolio.
8 properties
PortfolioByUserID.Holdings.CashReserve
object
2 properties
PortfoliosByUserID
array
A list of portfolios by userID.
portfolioID
string
The unique identifier of a portfolio.
clientFundID
string
A user defined identifier attached to the fund.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

drivewealth-portfolios-api-openapi.yml Raw ↑

Other APIs DriveWealth publishes across the network.

DriveWealth FIX API
DriveWealth Accounts API
DriveWealth Advisor Reports API
DriveWealth Asset Transfer API
DriveWealth Auth API
DriveWealth AutoPilot API
DriveWealth Beneficiaries API
DriveWealth Charts API
DriveWealth Commission Schedules API
DriveWealth Correspondent Reports API
DriveWealth Deposits API
DriveWealth Depth of Book API
Where this information came from

This is an independent, third-party profile of DriveWealth Portfolios API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.