Retrieve Account Summary Migration Guide

Overview

The endpoint GET /accounts/{accountID}/summary is deprecated.

To migrate, call the supported endpoints below and compose your own summary response object.

Endpoint Replacement Matrix

Deprecated endpointReplacement endpoint(s)Notes
GET /accounts/{accountID}/summaryGET /accounts/{accountID}/summary/moneySource of cash values and account-level money metadata.
GET /accounts/{accountID}/summaryGET /accounts/{accountID}/summary/marginSource of margin fields.
GET /accounts/{accountID}/summaryGET /accounts/{accountID}/summary/positionsSource of equity positions and valuation fields.
GET /accounts/{accountID}/summaryGET /accounts/{accountID}/summary/ordersSource of currently resting (pending) orders.
GET /accounts/{accountID}/summaryGET /accounts/{accountID}/transactionsSource of historical transaction activity (date-range query required).
GET /accounts/{accountID}/summaryGET /accounts/{accountID}Source of canonical account identity and account metadata.

Field Mapping

Use this mapping if your client currently expects the deprecated SummaryRes shape.

accountSummary

Deprecated fieldReplacement source
accountSummary.accountIDsummary/money.accountID (or summary/positions.accountID)
accountSummary.accountNosummary/money.accountNo (or summary/positions.accountNo)
accountSummary.tradingTypesummary/money.tradingType (or summary/positions.tradingType)
accountSummary.lastUpdatedsummary/money.updated (closest equivalent to legacy lastUpdated)
accountSummary.cashsummary/money.cash

margin

Deprecated fieldReplacement source
marginsummary/margin.margin

equity

Deprecated fieldReplacement source
equity.equityValuesummary/positions.equityValue
equity.equityPositionssummary/positions.equityPositions

orders

Deprecated fieldReplacement source
orderssummary/orders.orders

summary/orders returns only resting (pending) orders, which aligns with legacy summary behavior.

transactions

Deprecated fieldReplacement source
transactionstransactions response payload

Legacy transactions in the deprecated summary used transactionSumObj; GET /accounts/{accountID}/transactions returns transactionObj with overlapping but not identical field names.

Key normalization differences to handle in client code:

  • orderID (legacy) vs orderId (transactions endpoint)
  • commissions (legacy) vs commission (transactions endpoint)
  • GET /accounts/{accountID}/transactions requires from and to query parameters

Recommended Orchestration Pattern

  1. Call these endpoints in parallel:
    • GET /accounts/{accountID}/summary/money
    • GET /accounts/{accountID}/summary/margin
    • GET /accounts/{accountID}/summary/positions
    • GET /accounts/{accountID}/summary/orders
  2. Call GET /accounts/{accountID}/transactions?from={fromISODate}&to={toISODate} for transaction history window needed by your product.
  3. Optionally call GET /accounts/{accountID} if your UI also depends on additional account metadata outside the legacy summary payload.
  4. Build a compatibility object for downstream consumers.

Compatibility Object Example

{
  "accountSummary": {
    "accountID": "<from money.accountID>",
    "accountNo": "<from money.accountNo>",
    "tradingType": "<from money.tradingType>",
    "lastUpdated": "<from money.updated>",
    "cash": "<from money.cash>"
  },
  "margin": "<from margin.margin>",
  "equity": {
    "equityValue": "<from positions.equityValue>",
    "equityPositions": "<from positions.equityPositions>"
  },
  "orders": "<from orders.orders>",
  "transactions": "<from transactions endpoint payload>"
}

Migration Checklist

  • Replace all direct calls to GET /accounts/{accountID}/summary.
  • Add aggregation logic that composes the replacement payload.
  • Normalize transaction field names where needed (orderId/orderID, commission/commissions).
  • Add integration tests for:
    • cash and buying power values,
    • margin values,
    • positions valuation,
    • pending orders,
    • transactions date-window behavior.
  • Remove deprecated response-type dependencies from client models.


Did this page help you?