When updating multiple Sleeve Registrations, our batch workflow is faster and more scalable. This allows you to update multiple registrations at once, rather than sending a significant number of calls…
Continue Reading
The endpoint { PUT /api/v2/Portfolio/Portfolios/action/assignModel } – Accepts an array of Eclipse portfolioId and Eclipse modelId combinations. The call to Eclipse will assign the model to the Portfolio. Then if…
Trade Instances have some metadata fields that provide information on how a Trade Instance was created. These fields are optional in most API requests, if they are part of the…
Each Trade has an Action, like Buy or Sell, that is generally passed around in API JSON as an Id value. Occasionally, you will see the string value in some…
In some cases, Eclipse APIs return trade errors just as a set of Id/Argument pairs in JSON. Those will look like this: The the meaningful part of the errors are…
The Quick Trade tool in Eclipse is used to create single buy or sell trades in an account. It can also be used to import a list of buy and…
Purpose: Managing a large list of models or using the complexity of the model structure within Eclipse can be a challenge. This article will guide you through how to create…
The endpoint { PUT /api/v2/Portfolio/Portfolios/action/setPortfolioTradeBlock } – Accepts an array of portfolio.id and doNotTrade. The call to Eclipse will toggle trade blocked on the portfolio and will sync to Orion…
The endpoint { PUT api/v2/account/accounts/action/setAccountTradeBlock } – Accepts an array of account.id, isDoNotBuySell, isCustodialRestriction. The call to Eclipse will toggle trade block in Eclipse and sync to Orion Connect. id…
To get model details for Eclipse models, you would use the below endpoint: GET https://baseurl/v1/modeling/models/<modelid> property description required datatype <modelid> Model ID Yes Integer Below is an example for a…