If none is specified, the default sorting direction is descending for timestamp and numeric fields and ascending otherwise. The value can be asc to specify an ascending direction or desc to specify a descending direction. The sorting direction, which can be ascending or descending. The value of sort can be one of the names of the fields included in the response. These are the parameters that let you control how you want the sorting feature to behave: Name
To retrieve the list of public APIs that have been updated during a specific time interval, showing the most recently updated first, you would GET /apis?isPublic=true&since=T00:00:00+01:00&sort=updatedAt. You can, however, combine filtering and sorting to retrieve the results. Unlike filtering, where you can combine multiple parameters, sorting is limited to a single parameter at a time. The value of another parameter defines the sorting direction that can be ascending or descending. Sorting works by reading the value of a parameter that defines which field is used to sort the results. Only return APIs whose description includes the given value. Only return APIs whose summary includes the given value. Only return APIs whose name includes the given value. Public APIs have the isPublic value true private APIs have the isPublic value false. Only return APIs with the corresponding privacy state. Only return APIs that have been updated by the user ID represented by the given value. Only return APIs that have been created by the user ID represented by the given value.
#FILM POSTMAN ISO#
Time is represented using the ISO 8601 date and time format. Only return APIs that have been updated before this time. Only return APIs that have been updated after this time. Here are all the parameters that we’re adding that you can use to create your own filtering combinations: Name To get all the public APIs that have been updated during a specific time interval you would GET /apis?isPublic=true&since=T00:00:00+01:00&until=T00:00:00+01:00. If you employ more than one parameter, the filtering will be done using a logic AND on the combination of parameters.
#FILM POSTMAN HOW TO#
How to filter your APIsįiltering works by reading the value of a parameter and applying it as the filter to the corresponding response field. Keep reading to know more about how filtering and sorting work. “Being able to filter and sort the APIs during retrieval help us provide the best user experience to all API consumers when they are looking for a specific schema” says Fabrizio Ferri Benedetti, lead technical writer at Ohpen. With this latest feature, Ohpen, one of Postman’s customers, improved an internal tool to share and document OpenAPI specifications. Together, filtering and sorting let you access your APIs in ways that make more sense to your particular use case. Sorting, on the other hand, is a totally new feature that opens new possibilities. By combining filtering and sorting, you can obtain the filtered list of APIs showing the most recently updated APIs first.Įven though filtering APIs by workspace was already possible, we eventually added the ability to filter by most other fields. With sorting, you can define which field you want to sort by and the sorting direction. For instance, you can retrieve all the public APIs that have been updated during a specific time interval. You can easily apply a combination of filters using HTTP query parameters on the Postman API “Get all APIs” request. Filtering and sorting APIs using the Postman API gives you the ability to decide which APIs you want to retrieve and how to organize them.
0 kommentar(er)
