Amazon SP-API pagination returns same results with new nextToken — how to properly fetch next page?

[msrnayeem02]

I'm using the Amazon Selling Partner API (/listings/2021-08-01/items/{sellerId}) to fetch my product listings. I'm handling pagination using the nextToken parameter. My API fetch code looks like this:

async getListingsItems(nextToken?: string): Promise<any> {
  const path = `/listings/2021-08-01/items/${this.sellerId}`;
  const params = new URLSearchParams({
    marketplaceIds: this.marketplaceId,
    includedData: 'summaries,attributes,issues,offers,fulfillmentAvailability,procurement',
    limit: '20',
  });
  if (nextToken) {
    params.append('nextToken', nextToken);
  }

  const queryParams = params.toString();
  const headers = await this.authService.createSignedHeaders('GET', path, queryParams);
  const response = await axios.get(`${this.endpoint}${path}?${queryParams}`, { headers });
  return response.data;
}

When I hit my endpoint (/api/amazon/products), I get the expected response:

{
  "success": true,
  "products": 10,
  "data": {
    "numberOfResults": 51500,
    "pagination": {
      "nextToken": "someTokenHere"
    },
    "items": [
      { "sku": "acs-1524", ... }
    ]
  }
}

But when I call the same API again using that nextToken, I get the same products again, although the API returns a new nextToken. It keeps going in a loop — returning the same items but giving new nextToken each time.

Questions:

Is there something I’m missing in how Amazon SP-API handles pagination?

How can I ensure I get the next page of products, not repeated ones?

Environment:

Node.js + Express

[ritikacd]

Hi @msrnayeem02

Please ensure that the nextToken is properly encoded before including it in the searchListingsItems API call to retrieve data from subsequent pages. Could you confirm if this is already being done on your end?

Thanks,
Ritika
Selling Partner Developer Services

[pandjtrading]

According to the doc @ritikacd linked to the API doc, the correct query parameter name for nextToken is actually "pageToken"
just a design question - Why would the engineers decide to subvert expectations on this? Why call it nextToken in the response, then pageToken for the request?

[ritikacd]

Hi @pandjtrading

This is because the pageToken can be used to retrieve results from either the next page or the previous page. Users can pass the nextToken or previousToken as the value for the pageToken parameter in the next request, depending on the direction they want to navigate.

Thanks,
Ritika