Skip to main content
Manage and query portfolios for virtual users — abstracted identities that represent balance-tracking or CEX-linked accounts. Virtual user endpoints follow the same patterns as Portfolio but use virtual:<id> addresses.
Pro subscription required. Virtual users are a Pro feature. Create and manage them in the Octav Pro app — the API provides read-only access.
Interactive Playground: Test these endpoints in the API Playground. Get your API key at data.octav.fi
Cost: 1 credit per call (list) · 1 credit per virtual user address (portfolio)

List Virtual Users

Returns all virtual users belonging to the authenticated API user.

Endpoint

Parameters

No query parameters required — returns all virtual users for the authenticated user.

Response

Returns an array of virtual user objects.
address
string
Virtual user identifier in virtual:<id> format. Use this value in the portfolio endpoint’s addresses parameter.
type
string
The virtual user type (e.g. BALANCE, CEX)
label
string
User-defined label for the virtual user

Example Request

Example Response


Virtual Users Portfolio

Fetch portfolios for one or more virtual users. Works identically to GET /v1/portfolio but uses virtual user addresses instead of wallet addresses.

Endpoint

Parameters

addresses
string
required
Comma-separated virtual user addresses (from the list endpoint). Format: virtual:<id>. Max 10.
aggregated
boolean
default:"false"
Return a single reduced portfolio across all virtual usersWhen true, returns a single-element array with merged holdings from all specified virtual users
waitForSync
boolean
default:"false"
Wait for fresh data if cache is stale
  • false: Return cached data immediately (recommended)
  • true: Wait for sync if data is older than 1 minute
includeImages
boolean
default:"false"
Include image URLs for chains, assets, and protocolsUseful for displaying logos in your application UI
includeExplorerUrls
boolean
default:"false"
Include blockchain explorer URLs for assets and transactionsLinks to Etherscan, Arbiscan, etc. for easy navigation

Response

Same portfolio schema as GET /v1/portfolio. Returns an array of portfolio objects (one per virtual user), or a single-element array if aggregated=true.

Portfolio Object

address
string
The virtual user address (virtual:<id>)
networth
string
Total portfolio net worth in USD
cashBalance
string
Available cash balance
dailyIncome
string
Income generated today
dailyExpense
string
Expenses incurred today
fees
string
Total fees in native asset
feesFiat
string
Total fees in USD
lastUpdated
string
Last sync timestamp (milliseconds since epoch)
openPnl
string
Unrealized profit/loss (if available, otherwise “N/A”)
closedPnl
string
Realized profit/loss (if available, otherwise “N/A”)
totalCostBasis
string
Total cost basis of holdings (if available, otherwise “N/A”)
assetByProtocols
object
Assets organized by protocol (wallet, lending, staking, etc.)Each protocol contains:
  • key: Protocol identifier
  • name: Protocol display name
  • value: Total value in USD
  • assets[]: Array of asset holdings
chains
object
Assets organized by blockchainEach chain contains:
  • key: Chain identifier (e.g., “ethereum”, “arbitrum”)
  • name: Chain display name
  • value: Total value on this chain
  • protocols[]: Protocols with positions on this chain

Example Request

Example Response


Data Freshness

The Virtual Users Portfolio endpoint uses the same caching strategy as Portfolio:
Cache Duration: 1 minuteWhen data is less than 1 minute old:
  • Cached data returned immediately
  • Response time: under 100ms
When data is more than 1 minute old:
  • Cached data returned immediately
  • Background sync initiated for next request
  • Next request gets fresh data
With waitForSync=true:
  • Waits for sync if data is stale
  • Returns data less than 1 minute old
  • Response time: Variable (1-10 seconds)
For most use cases:
  • Use default waitForSync=false
  • Data fresher than 1 minute is sufficient
  • Fast response times
For real-time tracking:
  • Set waitForSync=true when you need the absolute latest data
  • Accept longer response times
  • Consider rate limits

Use Cases

Discover virtual users and fetch their portfolios in a single flow:

Error Responses

Invalid parameters provided.
Common causes:
  • Missing addresses parameter (portfolio endpoint)
  • Invalid address format (must be virtual:<id>)
  • More than 10 addresses in single request
Authentication failed.
Solution: Check your API key in the Authorization header
Attempted to access virtual users that don’t belong to the authenticated API user.
Solution: Only use virtual user addresses returned by GET /v1/virtual-users for your API key
Rate limit exceeded.
Solution: Wait for the specified time or implement retry logic
Insufficient credits.
Solution: Purchase more credits at data.octav.fi

Portfolio

Retrieve portfolio holdings for wallet addresses

Historical Portfolio

View portfolio value at specific dates

Status

Check when portfolio was last synced

Credits

Check your remaining API credits