The Benchmarks resource represents a collection of benchmarks accessible to the logged-in user. Benchmarks in the collection can include system owned ones, those that are owned by the user, and those that are owned by other users and currently shared to the identified user.

Requests for the Benchmarks resource always contain information regarding how the user’s benchmarks are to be filtered, ordered and sliced before being returned in a response. Unlike Portfolios or Classifiers, Benchmarks must be filtered to provide a search criteria as there are too many to enumerate system-wide. These instructions may be supplied by the client application (when using a link whose link relation is benchmarks-query), or by the service itself when emitting a non-query link (e.g. a link to the next page of benchmarks).

The underlying collection is first filtered. The filtered set is then ordered. Finally the ordered set is sliced by skipping N benchmarks and taking M benchmarks. If not all of the ordered set is returned in a response, and if N is a multiple of M (e.g. skip 8, take 4), then the benchmarks in the resource representation are paged. A paged collection will include links to the first and last pages, and optionally to the previous and/or next pages.

See Client-defined resource pagination via $skip and $top OData system query options in the Knowledge Base for important information about paging.

If no ordering and slicing information is contained in a request, then defaults are used:- ordered by name; take a maximum of 100 benchmarks. Note that the web service imposes a maximum ‘take limit’ of 100 benchmarks for all requests for the resource: it is not possible to retrieve more than 100 benchmarks in any one response.

For more information on filtering, ordering and slicing, refer to the documentation for the benchmarks-query link relation.

The resource representation includes details such as the name, unique identifier, code and owner name of each benchmark.

Media types

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


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

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

The Benchmarks resource links to the Service resource. It also links to itself in a variety of different ways. To do so, its resource representations use link relations:-

  • service
  • self
  • first
  • next
  • prev
  • last
  • benchmarks-query

The service link relation identifies the Service resource link.

The self link relation identifies the Benchmarks resource link, in which the representation is the same as the one that has been currently retrieved (so long as the underlying data on the server hasn’t changed).

The first and last link relations are present only if the retrieved collection is paged. They identify the first and last pages in the collection (at the time when the resource representation was generated).

The next and prev link relations are present only if the retrieved collection is paged and there is a next page and/or previous page in the collection (at the time when the resource representation was generated).

The benchmarks-query link relation identifies the resource link that allows a fresh query for benchmarks to be made. The fact that the link relation ends with “-query” indicates that a client-specified query must be made for benchmarks, when using this link. 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 with the exception of the {filter} query string which must be specified for this link. To apply filtering, ordering and slicing according to a subset of the ODATA system query options syntax, please refer to the benchmarks-query link relation’s documentation page.

All related resources are accessed using the HTTP GET method.

Update history

  • Added link to the Knowledge Base re. client-defined pagination - January 2019
  • Corrected the OData link - January 2019
  • Initial Version - December 2016

Annotated Representation (JSON)



Annotated Representation (XML)



Last updated: January 2019