Legacy Accounts

List the authenticated user's legacy accounts, grouped by loginid.

Endpoint

Status Codes

Error Responses

{
  "errors": [
    {
      "status": 404,
      "code": "NotFound",
      "message": "User has no legacy account mapping"
    }
  ],
  "meta": {
    "endpoint": "/trading/v1/options/legacy/accounts",
    "method": "GET",
    "timing": 16
  }
}

{
  "errors": [
    {
      "status": 409,
      "code": "MigrationPending",
      "message": "User migration is pending or has failed"
    }
  ],
  "meta": {
    "endpoint": "/trading/v1/options/legacy/accounts",
    "method": "GET",
    "timing": 19
  }
}

About legacy_accounts

The legacy_accounts endpoint list the authenticated user's legacy accounts, grouped by loginid.

Response Shape

The response is a single loginidsobject keyed by the user's legacy loginids. Each value is an array of accounts owned by that loginid, each with an account_id and currency. Loginids with no resolvable accounts are omitted from the response entirely.

When to Call

Use this endpoint to discover the legacy loginids you can pass to GET /trading/v1/options/legacy/statement. If the user's migration is pending or has failed, the request returns HTTP 409; if the user has no legacy mapping at all, it returns HTTP 404.