Note that the API call documentation says...   A token used by the server to indicate the start of the page. Often this is a timestamp or an ID but it is not limited to those. This parameter should not be defined by client applications. The link for the first, last, prev, or next page in the HTTP Link header should define it.   The link headers fro the first call will have the link to the next call in them, this includes the appropriate token needed, you can just take the link that is for the next page and do a get, or you can parse the link to extract the token value then use it to build your next request.   If you look at the explanation here https://developer.cisco.com/meraki/api-v1/pagination/#example it shows the link headers fro the initial call, and then how to use the 'next' link to get the next page of data and so on. You can see the parameter names and correct token values there for the first/next/last pages...   <https://api.meraki.com/api/v1/networks/N_1234/bluetoothClients?perPage=5&startingAfter=0>; rel=first, <https://api.meraki.com/api/v1/networks/N_1234/bluetoothClients?perPage=5&startingAfter=105>; rel=next, <https://api.meraki.com/api/v1/networks/N_1234/bluetoothClients?perPage=5&endingBefore=0>; rel=last       ... View more