Specify one of the following values:

The name of the parameter that you want to use for the paging operation. You can use a query parameter or a path parameter.

The page number that indicates the first page in the range, on which you want to perform the paging operation.

The page number that indicates the last page in the range, on which you want to perform the paging operation. The default is 10000.

An integer to increment the Page Parameter. Page Increment Factor must be same as the number of records being fetched per request. If the Page Increment Parameter option is not same as the number of records being fetched per request, you might have missing or duplicate records between two calls.

Specify an expression or a string to control paging. You can observe one of the following behaviors:

If you specify a string or an expression, the paging stops when the value matches with the page response. It does not parse the page that has matching end of response.
If you do not specify a string or an expression, the paging stops on reaching a page that has an empty or a Null response. If an empty or a Null response is never reached, the paging stops at the default end page.
If you specify both, End Page and End of Response Expression, the paging stops on whichever condition is met first.
If you do not specify End Page and End of Response Expression, the paging stops on reaching an empty or a Null response. If an empty or a Null response is never reached, the paging stops at the default end page.

Overrides the URL specified in the swagger specification. The override URL cannot have query parameters. When a path parameter is included in the Override URL, enclose the path parameter with curly brackets {}. For example:

Default is 100 KB. If the request is more than 100 KB, you can increase the cache size.

Memory available for the web service response. If the web service response contains many rows or columns, you might want to increase the cache size. Default is 100 KB.

Not Applicable.

Not Applicable.