Blogger API v3 : when calling /posts/search/, parameter nextPageToken is ignored

Env : javascript, using XMLHttpRequest and JSON API.

When calling {URL}/posts/?{parameters} :

• the 10 first items are returned
• if the response contains more than 10 items, an attribute { "nextPageToken":"xyz" } is added to the JSON data response.

Then when calling {URL}/posts/?{parameters}&pageToken={nextPageToken} :

• the response contains the next 10 items
• a new nextPageToken is returned until no more page

=> Looks like the expected behavior, working fine.

However: When calling {URL}/posts/search/?q={query_string}{parameters} :

• the 10 first items are returned
• if the response contains more than 10 items, an attribute { "nextPageToken":"xyz" } is added to the JSON data response.

Then when calling {URL}/posts/search/?q={query_string}{parameters}&pageToken={nextPageToken} : - the 10 first items are displayed again (ie not the next 10), - returned nextPageToken is the same than first call

Looks like pageToken is ignored for /posts/search/. Is this the expected behavior ? How to access items of /posts/search/ response returning more than 10 items?

[mortezaadi]

Definitely, it’s not a bug, though it needs more clarification, you can refer to this document from Blogger API v3.

to get the pagination work you need to call the API with maxResults={pageSize} then you will get an extra value in the response ‘nextPageToken’, you should use the value of this field and pass it with. ‘pageToken’ NOT ‘nextPageToken’

https://blablabla?maxResults=10&pageToken={VALUE_OF_NEXTPAGETOKEN}

when you reach the end of the list you won’t get the nextPageToken anymore and it means nothing more to fetch.

[meltsufin]

It doesn’t appear to be an issue with the library itself. If anything, it’s the service.