topic Re: Please tell me how to solve '429 - Too many requests'. in Network Platform API

Please tell me how to solve '429 - Too many requests'.

gwangjin.park — Mon, 19 Jul 2021 08:25:08 GMT

Hi,

I was collecting client information periodically using 'Get Network Clients'.

But suddenly, 'Too Many Requests' started to happen.

So I stopped all API calls and waited.

But it's been 3 hours and 'Too Many Requests' are still happening.

Even though there's only one API call.

What do I have to do to release that condition?

Let me know if anyone knows.

regards Gwangjin

Re: Please tell me how to solve '429 - Too many requests'.

inderdeepsingh1 — Mon, 19 Jul 2021 13:48:17 GMT

@gwangjin.park : Check this document

https://developer.cisco.com/meraki/api/#!rate-limit

Re: Please tell me how to solve '429 - Too many requests'.

Rasmus Hoffmann Birkelund — Mon, 19 Jul 2021 14:31:04 GMT

This is what I use..

The hardcoded status_code = 201, is only declared for testing purposes and its just "faking" a succesful POST towards the API.. Remove it, and uncomment the actual request().

...
                 for _ in range(MAX_RETRIES):
                    try:
                        resp.status_code = 201
                        # r = requests.request(
                        #         'POST',
                        #         url,
                        #         headers = headers,
                        #         data = payload
                        # )
                        if resp.status_code == 201:
                            if index < len(p_sitelist)-1:
                                LOGGER.info(f"[ Create Networks ]: Network {site['Network']} created successfully! On to Next..")
                                #print(f"Network {site['Network']} created successfully! On to Next..\n")
                                break
                            else:
                                LOGGER.info(f"[ Create Networks ]: No more networks to create.")
                                #print("No more networks to create.")
                                return              
                        elif resp.status_code == 429:
                            LOGGER.warning(f'[ Create Networks ]: Rate limited - Retrying after {r.headers["Retry-After"]}.')
                            #print(f'Rate limited - Retrying after {resp.headers["Retry-After"]}.')
                            time.sleep(int(resp.headers['Retry-After']))
                            continue
                        else:
                            LOGGER.critical(f'[ Create Networks ]: Unexpected status code: {r.status_code} returned from server.\n Msg: {r.text}')
                            raise SystemExit(f'Unexpected status code: {r.status_code} returned from server.\n Msg: {r.text}')
                    except Exception as e:
                        LOGGER.error("[ Create Networks ]: Unknown error..")
                        LOGGER.exception(e)
                        #pprint(e)
                        return ""

Re: Please tell me how to solve '429 - Too many requests'.

Philip D'Ath — Mon, 19 Jul 2021 20:14:13 GMT

Note that if you use the Python SDK it automatically retries on a 429 for you.

https://developer.cisco.com/meraki/api-v1/

Re: Please tell me how to solve '429 - Too many requests'.

gwangjin.park — Tue, 20 Jul 2021 01:51:25 GMT

I found out something new during the test.

In the company, "Too Many Requests" occurs when the Meraki Dashboard API is called.

But it's normal(status code : 200) to call the same API at home.

I think it's a restriction by IP.

Please let me know if you know what to do.

* PS : We can't change the company's IP.

Re: Please tell me how to solve '429 - Too many requests'.

xiaoyhu — Tue, 20 Jul 2021 12:46:31 GMT

There is a concurrency limit of 10 concurrent requests per IP.

It sounds like you are not the only one who is calling the same Meraki organization probably with a automation script.

Try to use the below endpoints to investigate.

Use 'getOrganizationApiRequestsOverview' to get an overview of API summary during a given timespan. Here is an example.

{

"responseCodeCounts": {

"200": 50000,

"201": 4000,

"204": 1000,

"400": 3500,

"404": 1500,

"429": 10000

}

Use 'getOrganizationApiRequests' to analyze details on what are those API calls, who is calling them from which IP. Below is an example of the output. You might need to create a script to analyze the output as there are tens of thousands of items in case of API being misused.

[

{

"adminId": "212406",

"method": "GET",

"host": "api.meraki.com",

"path": "/api/v0/organizations/33349/apiRequests",

"queryString": "timespan=604800",

"userAgent": "PostmanRuntime/7.6.0",

"ts": "2019-02-20T17:31:23Z",

"responseCode": 200,

"sourceIp": "123.123.123.1"

}

]

Once you identify the suspect admin ID, use 'getOrganizationAdmins' to get the email identity.

Re: Please tell me how to solve '429 - Too many requests'.

gwangjin.park — Wed, 21 Jul 2021 06:46:01 GMT

ShawnHu, thank you for your response.

First of all, I have something to say for sure.

1) No one calls the Meraki Dashboard API.

2) '429 - Too many requests' only occur in the company.

Two days later, '429 - Too Many Requests' are still occurring.

How can I solve this problem?

Again, no one is calling the Meraki Dashboard API.

regards Gwangjin

Re: Please tell me how to solve '429 - Too many requests'.

Philip D'Ath — Wed, 21 Jul 2021 21:01:36 GMT

Are you sure something in your code, perhaps somewhere else, is not in a tight loop making repeated API calls in succession?

If you chance to using the Python SDK this issue is likely to go away. Or at a minimum, you'll be able to enable a trace of the calls to see if you are making lots of calls close together.

Re: Please tell me how to solve '429 - Too many requests'.

Philip D'Ath — Wed, 21 Jul 2021 22:14:32 GMT

@John-on-API , another one.

Re: Please tell me how to solve '429 - Too many requests'.

John-on-API — Wed, 21 Jul 2021 22:21:58 GMT

I'd check your actual API usage. How many other users (or applications) have API keys? You have to share the budget with those other folks in the same org. Even if your usage hasn't changed, there are likely others using API more, thus competing with your usage.

In the API docs, check Organizations > Monitor > API Requests for the two endpoints that give you this info.