The wildcard filter in some cases also matches values in sub-entities, to make them more useful to the client. The Service Desk API GET /api/service_desk/tickets has special handling to include owner names and submitter names in the wildcard. To find out if this handling is available and for more information about the Service Desk API, see Service Desk API Reference.
Filters can be combined. The following example retrieves the machines that have the software title DEF installed and also have fields containing the ABC string:
Sorting is accomplished with the sorting query parameter. Commas can be used to separate multiple sorting requests. Each sorting request must give the sort entity and field. Optionally, a sort order can be specified. If the sort order is not specified, the default sort order is ASC (ascending). Sort requests are processed from left to right.
Sorting can be performed on the base entity as well as on any sub-entities. If sorting is indicated for a sub-entity that does not appear in the shaping clause, that sub-entity is automatically included at the standard shaping level. Any given shaping level overrides that value.
Sort the machines by their ID in a descending list, and retrieve the software for each machine. Shaping is not necessarily required here. It is assumed that since ordering was requested for the software, it is expected in the result set:
To apply paging, use the paging query parameter.
To limit the number of records returned, use the limit parameter. For example:
To indicate the index of the first returned record, use theoffset parameter. For example:
These two values are useful for consumers that display the records in a paged format. The values can appear in either order.