Pagination, Sorting, Filtering

Pagination

Clients may request a subset of results returned by a list resource in response to a GET request. This can be done by specifying two optional query string parameters: offset – a 0-based index of first object in the list to return (defaults to 0); and limit – number of objects to return in the result (defaults to 100).

Total count

By default, each list resource returns the total number of objects it contains before pagination is applied (but after any value filters are applied). This value is returned in X-Total-Count: <number> header; this makes it possible to obtain the object count without the actual results via a HEAD request, e.g.

X-Total-Count: 3

Field selection

It is possible to select a subset of fields (object properties) to return instead of all available fields. This can be done by specifying one or more "fields" parameters in the query string. The value of this parameter is a comma-separated list of property paths to include in the response. Each property path is a dot-separated list of object property names. E.g.,

fields=id,spkey,name&fields=endpoints.id,endpoints.name

Sorting

Collection results may be explicitly sorted by one or more properties by specifying them in the "sort" query string parameter. It is a comma-separated list of property names optionally followed by :asc or :desc to specify sort direction (defaults to asc).

Date format details

When filtering the data for Users, Applications, Package Keys and Portal Access Groups, you can use Created and Updated date ranges through the API Calls. The following are the date formats which are allowed/recommended in the API Calls as request param to fetch the data:

Note: Using the date format of yyyy-mm-ddThh:mm:sszzz is the most reliable format as the API will return an accurate response since the data gets stored in the DB in PST format.

Query string parameter summary