In the previous tutorials of this series, we showed you how you can sample and connect to a REST API, query the REST API using SQL and how you can change the metadata by editing the configuration file, when you use Progress Autonomous REST Connector. Before you start this tutorial, we highly recommend you go through the below tutorials first.
When you want to access the data from REST API, where it’s exposing large amount of data – most of the APIs implement paging to reduce loads on the server and abuse. In the previous tutorials, when you queried Yelp’s API, you were only seeing data from first page of the API response. Often you would need to access the data beyond the first page and in this tutorial, we will show you how you can get the data beyond the first page when you use Progress Autonomous REST connector to query the Yelp’s REST API using SQL.
The maximum page size in rows. Eg: 50
The number of the first row. The default is 0; however, some systems begin numbering rows at 1.
The name of the URI parameter that contains the page size.
The name of the URI parameter that contains the starting row number for this set of rows.
The maximum page size in rows.
The number of the first page. The default is 0; however, some systems begin numbering pages at 1.
Here #maximumPageSize is set to 50 because Yelp will only provide a maximum of 50 results per page. #firstrow is set to 0, as yelp starts the results with 0. #pageSizeParameter is set to the value “limit” and #rowOffsetParameter is set to “offset” as per the documentation of Yelp.
In the next tutorial, we will walk you through how you can push down any filters to REST API using query parameters. If you have any questions or issues until now, please feel free to talk to us.