OK, after some testing, I found that I am wrong about using the Python list for the vlans. They want a string with comma separated values. Your data needs to look like this:   {"enabled": true, "type": "trunk", "dropUntaggedTraffic": true, "allowedVlans": "1,128"}   It also will not let you just use any values for the vlans. They have to already exist for the MX. On the device I was using for testing vlans 1 and 128 were already defined, so updating a port to use one, both, or 'any' worked fine. If I tried to assign "10" as a vlan, it would give me an error 400. ... View more

OK, I will break this down the way I process it and keep the specific code out of it.   When I call my function, I pass it the URL for the endpoint (https://n11.meraki.com/api/v0/networks/N_555555555555555/clients) and the query information (timespan=30&perPage=1000)   The function starts a loop and calls the endpoint with this data. The first 1000 entries are returned. It saves that data. It then looks at the header.list and checks for "rel=next". If it finds it, it then gets whatever the token value is associated and then modifies the query to include it, using your example (timespan=30&perPages=1000&startingAfter=ka1710e)   It then goes back to the top of the loop, checks to see if it is done, and then calls the endpoint again with the new query values. It gets the next 1000 clients and concatenates the data to the end of the previous page. Then it checks for "rel=next" again. If it finds it, it gets the new token (k17db29) and updates the query to be timespan=30&perPages=1000&startingAfter=k17db29)   It goes to the top of the loop and sees it is not done. Calls the endpoint again with this query. Get the next page of data and concatenates it. Let's say this is the last page. It checks for "rel=next" and does not find it. It sets the flag to tell the loop it is done and returns to the top of the loop. The loop sees it is done and exits the loop. The function then returns all of the data it collected (3 pages worth) so it can be processed.   Does that make it a bit clearer? ... View more

What @joincidence is talking about is the perPage value you need to specify to get the client list with this endpoint. It indicates how many results will be on a "page". For some reason, Meraki assumes that data from this endpoint will be displayed on a webpage and you will move through it using "Prev" and "Next" links. Calling the endpoint gives you the first page of data. In this case the first 1000 clients. The question is how do you get the rest of the data?   I had this same problem and this is what I found. Now, this is using Python, but the data should still be in the same place regardless of the language. In the information that is returned by the requests.request or requests.get is a field called "headers". Inside of this is a another field called "Link" (headers['Link']) that contains all of the information for the "Prev" and "Next" links. In this data is the token values you need to move back and forth through the data. By getting the token (this can be a device ID, timestamp, or some other piece of data) you can specify it with the "startingAfter" parameter in another API call to the client endpoint and get the next "page" of data. You just have to keep getting the token for "Next" and making another call, until you no longer have a "Next" link. Then you have moved though all of the data. If you concatenate all of the results together as you get them, you will have all of the results in a single variable.   Here is the function I wrote to do this:   # This function takes the API URL and query string. It returns all of the JSON data from the API request that has # been broken up into pages of data. def GetPages(url,query):    data = []    done = False    while done != True:    try:       ret = requests.request('GET', url, headers=g_header, params=query)    except requests.exceptions.ConnectionError:       print('A connection error has occurred while getting the page information.\n')       return None # Append the new data to the existing.    data += ErrorCheck(ret) # Get the page URLs from the HTTP header of the API call and split it into the URLs.    pages = ret.headers['Link'].split(',') # See if there is a page for the 'next' page of data.    page = next((i for i in pages if 'rel=next' in i), None)    if page != None: # Isolate the token and then add it to the new query.       token = page.split('startingAfter=')[1]       token = token.split('&')[0]       query['startingAfter'] = token    else:       done = True return data   You would call this with the full endpoint path and the the query info that will go into the GET ({'timespan':'30','perPage':'1000'}). It makes all of the API calls and collects the results into a single variable, which is returned. Now, the call to ErrorCheck that is in there is another of my functions that just converts the raw data to JSON and checks for errors. The variable g_header in the requests call is a global variable that contains my API key information.   Hope this helps. If there are any questions about this explanation or the code, please let me know. ... View more