Sync Holdings on a Sub Account

POST /api/v1/plans/{plan_uuid}/sub-accounts/{subAccount_uuid}/sync-holdings

Headers

Path parameters

application/json

Body Required

  • holdings array[string] Required

    Holdings array to sync. all other holdings on this sub account will be marked as inactive

  • portfolio_name string

    Optional name of the portfolio when the holdings are synced

  • is_proposed_portfolio boolean

    Denotes if the portfolio that is created should be proposed or not.

Responses

  • 202 application/json

    Additional properties are allowed.
POST /api/v1/plans/{plan_uuid}/sub-accounts/{subAccount_uuid}/sync-holdings 
curl \
 -X POST https://api.plannrcrm.com/api/v1/plans/plan_uuid/sub-accounts/subAccount_uuid/sync-holdings \
 -H "Authorization: Bearer {OAUTH_ACCESS_TOKEN or PERSONAL_ACCESS_TOKEN}" \
 -H "Content-Type: application/json" \
 -H "Accept: application/json" \
 -d '{"holdings":[{"citi":"ABC12345","isin":"ABC12345","sedol":"ABC12345","units":100,"sector":"Europe","provider":"Transact","fund_name":"Cash","is_active":true,"reference":"C4$4","unit_price":1,"purchase_price":1}],"portfolio_name":"Proposed Holdings 2023","is_proposed_portfolio":true}'
Request examples 
# Headers
Authorization: Bearer {OAUTH_ACCESS_TOKEN or PERSONAL_ACCESS_TOKEN}
Content-Type: application/json
Accept: application/json

# Payload
{
  "holdings": [
    {
      "citi": "ABC12345",
      "isin": "ABC12345",
      "sedol": "ABC12345",
      "units": 100,
      "sector": "Europe",
      "provider": "Transact",
      "fund_name": "Cash",
      "is_active": true,
      "reference": "C4$4",
      "unit_price": 1,
      "purchase_price": 1
    }
  ],
  "portfolio_name": "Proposed Holdings 2023",
  "is_proposed_portfolio": true
}
Response examples (202) 
{}