Update the description of the interestRateInPercent field for the Loan Asset data model, to make it clearer that the sign matters, and exactly what it means.
Fix examples for GET endpoints for asset classes and detailed asset classes, to properly reflect that the endpoints return single objects and not arrays of objects.
Add documentation for asset classes, both regular Asset Classes and Detailed Asset Classes, and the associated GET /asset-classes/:id and GET /asset-classes-detailed/:id endpoints.
Add support for expanding Holding and Performance data by asset class and detailed asset class.
Add asset class and detailed asset class relationships to Asset Holding model.
Update the description for the Loan Asset data model, to make it clearer that the sign of the principalAmount field matters, and exactly what it means.
Fix an issue with a missing comma in the examples for how to get and create Loan assets.
Update FX Forward Physical Delivery Transaction
to reflect an FX forward physical delivery as a single transactions resource
instead of two distinct transactions (one for each side of the currency pair).
Prepend URLs in all HTTP request examples with "/api/", reflecting correct
resource locations.
Update FX spot data model to
reflect an FX spot trade as a single transaction resource instead of two
distinct transactions (one for each side of the currency pair).
Add assetCcyToAccountCcyExchangeRate to the transaction models with asset relationships. (Not yet supported as input parameter for POST /transactions).
Add excludeFromReporting flag to the account model.
"assets" is being deprecated as a possible value of the expand parameter
when calling GET /holdings/reporting-entities/:id. Use the dedicated
asset-level endpoint GET /assets-holdings/reporting-entities/:id instead.
Adjust request examples of PATCH /accounts/:id, PATCH /depositories/:id,
PATCH /reporting-entities/:id, and PATCH /portfolios/:id to exclude relationships that cannot be updated.
Included asset data from GET /performance/reporting-entities/:id and GET /holdings/reporting-entites/:id, i.e. when &include=asset is passed to
those endpoints, use the same data model as GET /assets/:id.
Adjust request example of POST /legal-entities/:id/depositories to include
the required "accounts" relationship.
Remove the single asset model in favor of specialized models.
Remove deprecated endpoints GET /clients/:id/portfolios, GET /holdings,
GET /holdings/reporting-entities/:id/assets, and GET /performance/reporting-entities/:id/assets as well as associated data models
Asset Holding and Asset Performance.
Support inclusion of asset data when fetching holdings (GET /holdings/reporting-entities/:id) and performance (GET /performance/reporting-entities/:id) by passing "&include=asset" as a query
parameter.
Use camelCase instead of kebab-case for the JSON property representing the
relationship from Performance to Reporting Entity, i.e. "reportingEntity"
instead of "reporting-entity".
Client-related data models are extended with relationships.
Documentation of client-related resources is split into two branches, legal structure and reporting structure, and documentation of the following endpoints is added:
Holding and performance relationships are no longer represented as a "subects" list. Instead, "depository", "portfolio", "reportingEntity", and "asset" relationships appear directly in the "relationships" object.
Endpoints that are not yet available are tagged as such throughout the documentation.