The Segments Tree Node resource represents a node in the Segments Tree, which contains analysis results data in the form of segments, securities and measure values.
A portfolio analysis with results data always exposes a hierarchical collection of segments and securities, known as the Segments Tree. Through this resource, the web service affords access to the Segments Tree one node at a time, starting at the root node, which equates to the Total segment. (An alternative way of accessing the Segments Tree is via the Whole Segments Tree resource, introduced in September 2014. See the documentation for that resource and its link relation for more details.)
Any one node in the Segments Tree represents a segment, either the Total segment or a child segment (or the child of a child, and so on). A node cannot represent a security, but any node can contain securities. In addition, tree node representations can contain client-requested measures (e.g. Portfolio Return; Alpha; Beta; Weight Mean).
The key to understanding the Segments Tree Node resource is knowing what data can be included in any one node, and how to formulate a query for that data. To this end, please see the documentation for the
segments-tree-root-node-query link relation, which contains the full details.
See the annotated representations below for details of how the requested information is contained in XML and JSON representations of the resource.
The Segments Tree Node resource is exposed via XML and JSON representations, which have the following media type names:- > application/vnd.statpro.revolution.api.segments-tree-node+json
When a response is received from the web service with status 200 (= OK), the fact that the response contains a Segments Tree Node resource representation is indicated by the presence of one of these two response headers:- > Content-Type: application/vnd.statpro.revolution.api.segments-tree-node+json; charset=utf-8
Content-Type: application/vnd.statpro.revolution.api.segments-tree-node+xml; charset=utf-8
The Segments Tree Node resource links to the Service, Portfolios and Time Series resources (and to itself). To do so, its resource representations use link relations:-
self link relation is used to identify links to a) the current resource representation, and b) other nodes at one level down in the tree that represent the current node’s child segments. See the annotated representations below for more details.
service link relation identifies the Service resource link.
portfolios-query link relation identifies the link that allows a new query for portfolios to be made.
segments-tree-root-node-query link relation identifies the link that allows a new query for data from the Segments Tree to be made, starting (again) at the root node.
time-series-query link relation identifies links that allow a client application to extract time series data for one or more measures for a) the segment that the node represents, and b) this node’s child segments, if included and c) this node’s securities, if included. See the annotated representations below for more details.
last link relations identify links that target versions of the current resource representation that contain the next, previous, first and last pages of the node’s children (either child segments or securities) - if included, and if paged.
All related resources are accessed using the HTTP GET method.
time-series-querylinks from within
securitiesso that time series data can now be extracted from within individual securities - Mar 2019
totalFilteredItemsindicating the total number of child segments or securities available across all pages (when multiple pages are available).
whole-segments-tree-querylink relation - September 2014
eulalink relation removed - September 2013
Last updated: Mar 2019