Paging issue in webservices connector

[Orlandoroman]

Hi all!

I am setting up a webservices connector for an application and wanted some help with paging.

Here is the outcome of the account aggregation list users (dummy urls):
{
“message”: “OK”,
“firstPageUri”: “https://api.url.net/rest/users/?pageNumber=1”,
“nextPageUri”: “https://api.url.net/rest/users/?pageNumber=2”,
“lastPageUri”: “URL/pageNumber=16”,
“page”: {
“pageSize”: 10,
“start”: 0,
“data”: [

Initially the aggregation was pulling in 10 accounts. I tried the following paging rule and it did bring in 8 more accounts for a total of 18, but the source has 100+ accounts.

TERMINATE_IF $response.nextPageUri$ == NULL
$endpoint.fullUrl$ = $response.lastPageUri$

Any help would be much appreciated

[Swegmann (Sebastian Wegmann)]

Hello Orlando,

Have you tried the request in, for example, Postman to see if you get the same result there?

[Orlandoroman]

The JSON above is from postman

[Swegmann (Sebastian Wegmann)]

Aha I see so the pagination is not working properly in Postman.

Do you have a swagger-page for the API where you can see exactly what is needed to paginate properly for the specific API? If not sensitive you can share it with me and I can have a look.

When just looking at the JSON-payload it seems like you are only fetcing the first 2 pages, with a maximum of 10 objects per page. It’s difficult to know however without the documentation.

[Orlandoroman]

Here is the swagger Swagger UI
and this is the newer version of their API documentation List Users

Yes this API page size is 10.

[jesvin90 (Jesvin Joseph)]

Hi @Orlandoroman,

Can you try this

TERMINATE_IF $response.nextPageUri$ == NULL
$endpoint.fullUrl$ = $response.nextPageUri$

Also, here is a document you can refer to :

[Orlandoroman]

Hi Jesvin! This pulled in the full amount of accounts. Thanks a ton!