The Service resource is the entry-point resource of the Web API (aka web service). It is identified by the entry-point URI,, and accessed using the HTTP GET method. When a client application starts to use the web service, it should always start at the Service resource. From there it can move forwards to other resources, using service-supplied links.

The Service resource offers the following:-

  • a count of the user’s portfolios (the portfolios that the user owns, plus the portfolios that are shared to him/her by other users);
  • a link that allows the user’s portfolios to be retrieved via a client-specified query.
  • Optionally, a link providing access to the full list of available reporting tags associated to portfolios in the authenticated user’s tenancy. This collection of distinct reporting tags is represented by the Portfolio Reporting Tags resource. If no reporting tags have been imported against any portfolios, then this link will not be exposed.

For convenience, every other resource in the web service exposes a link to the Service resource, using the same entry-point URI.

Media types

The Service resource is exposed via XML and JSON representations, which have the following media type names:- > application/vnd.statpro.revolution.api.service+json


When a response is received from the web service with status 200 (= OK), the fact that the response contains a Service resource representation is indicated by the presence of one of these two response headers:- > Content-Type: application/vnd.statpro.revolution.api.service+json; charset=utf-8

Content-Type: application/vnd.statpro.revolution.api.service+xml; charset=utf-8

The Service resource links to the Porfolios resources (and to itself). To do so, its resource representations use link relations:-

  • self
  • portfolios-query

The self link relation identifies the Service resource link.

The portfolios-query link relation identifies the Portfolios resource link. The fact that the link relation ends with “-query” indicates that a client-specified query must be made for portfolios. This is done by replacing all the text-replacement parts of the link’s query string (such as {filter}) with values. Specifying invalid values will result in a 400 (= Bad Request) response. All the text replacement parts of the query string can be replaced with the empty string. To apply filtering, ordering and slicing according to a subset of the ODATA system query options syntax, please refer to the portfolios-query link relation’s documentation page.

The portfolio-reporting-tags link relation identifiers the Portfolio Reporting Tags resource link. This resource represents the distinct collection of reporting tags available in the authenticated user’s tenancy.

All related resources (including the Service resource itself) are accessed using the HTTP GET method.

Update history

  • Corrected the OData link - January 2019
  • The outgoing link to the Portfolio Analysis Status Bulk resource has been modified to use a placeholder of {analysisContext} rather than being hard-wired to ‘default’ - July 2018
  • Added optional link for the portfolio reporting tags resource - February 2015
  • Information about EULA removed - September 2013
  • Initial Version - February 2013

Annotated Representation (JSON)



Annotated Representation (XML)



Last updated: January 2019