Organization Configuration Changes API pagination

[amattison]

When making the API call for the organization configuration changes, using the demo API key, I'm looking for all the changes made in the past year (the largest timespan possible) and using the highest/default entries per page of 5000. I'm specifying the t0 and t1 one values in "YYYY-MM-DDTHH:mm:ss" format (I've also tried using the Epoch Unix in seconds. I'm not sure if one is better than the other). I'm receiving valid responses and checking the headers for a "rel=next" link for the next page and using that URL for my next request, until there is no more next page links. The issues I'm having are as follows:

• often a next page is available, even when the first page contains fewer than 5000 entries
• on occasion, the next page will return headers with identical links, resulting in an infinite loop
  • on the last run, this is occurring when trying to reach -https://n22.meraki.com/api/v1/organizations/575334852396583237/configurationChanges?perPage=5000&sta...
  • The error seems to occur consistently on this call, regardless of t0 and t1 being specified, at the time of writing

Are these errors on my end or is there a flaw in the API?

[levmason]

Yes I'm experiencing this bug as well...any hope for a fix?

[John_on_API]

Hello @amattison ,

I cannot confirm this on my end, but what you've described here could be a bug. Please report it through Meraki support with steps to reproduce the issue.

Kindly,

John