OData supports various kinds of query options as query parameters. For instance, $orderby can be used for sorting the query results. Here is an example:
GET http://localhost:8080/hrapp/odata/Departments?$orderby=
DepartmentName HTTP/1.1
Similarly, you can use the $select option for limiting the attributes on the entity resources returned by a REST API. Here is an example:
GET http://localhost:8080/hrapp/odata/Departments? $orderby=DepartmentName&$select=DepartmentName,ManagerId HTTP/1.1
Some of the frequently used query options are listed in the following table:
|
Query Option |
Description |
Example |
|
$filter |
This option allows the client to filter a collection of resources. |
/Employees? $filter=FirstName eq 'Jobinesh' |
|
$expand |
This option includes the specified (child) resource in line with the retrieved resources. |
/Departments(10)?$expand= Employees |
|
$select |
This option includes the supplied attributes alone in the resulting entity. |
/Departments?$select=Name, LocationId |
|
$orderby |
This option sorts the query result by one or more attributes. |
Departments?$orderby= DepartmentName desc |
|
$top |
This option returns only the specified number of items (from the top) in the result collection. |
Departments?$top=10 |
|
$skip |
This option indicates how many items need to be skipped from the top while returning the result. |
Departments?$skip=10 |
|
$count |
This option indicates the total number of items in the result. |
Departments/$count |