Chrome-Stats

フリーミアム
よって Hao Nguyen | 更新済み 10 days ago | Data
人気

9.1 / 10

レイテンシー

409ms

サービスレベル

99%

Health Check

N/A

すべてのディスカッションに戻る

429 error on Details endpoint

Rapid account: Codefuel Dev
CodefuelDev
10 months ago

Hi.

I am trying to make 500 requests, and because of the limit of 100 requests per minute I told my code to wait for 70 seconds after every 90 requests (just to be sure).

However I still get Too Many Requests Error (429 error) on 20% of the requests.

Do you have any suggestions? Am I doing something wrong?

Thank you,
Shai

Rapid account: Admin Qo Wnih Uxr
admin-QoWnihUxr Commented 9 months ago

Hi Shai. I reached out to RapidAPI, and they said it might be a temporary issue on their side. The error should be gone now.

Rapid account: Codefuel Dev
CodefuelDev Commented 10 months ago

Thank you very much Hao.

Please keep my updated if there is anything new at shaio@codefuel.com

Shai

Rapid account: Admin Qo Wnih Uxr
admin-QoWnihUxr Commented 10 months ago

Hi Shai,

Thank you for your example request. I tried to reproduce based on your description, and I was able to hit the 429 error as well. Upon debugging, it appears that the 429 error is coming from RapidAPI proxy. It seems like RapidAPI tends to be stricter than the rate limit that the developer has specified. I try raising the rate limit for the premium plan to 300/minutes as well as removing it, yet I can still hit the 429 error.

I will reach out to RapidAPI to see what they say. In the mean time, I would recommend catching the 429 error, and retry after a few minutes.

Best,
Hao

Rapid account: Codefuel Dev
CodefuelDev Commented 10 months ago

example request:

GET /api/detail?id=gnkndpcagheiihcmllkdiadioglnonoj HTTP/1.1
Accept: application/json, text/plain, */*
X-RapidAPI-Host: chrome-stats.p.rapidapi.com
X-RapidAPI-Key: ****************************
platform: chrome
User-Agent: axios/1.4.0
Accept-Encoding: gzip, compress, deflate, br
Host: chrome-stats.p.rapidapi.com
Connection: close

response:

{
  "message": "Request failed with status code 429",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 429\n ..... ",
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "adapter": [
      "xhr",
      "http"
    ],
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 0,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "env": {
      "Blob": null
    },
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "X-RapidAPI-Host": "chrome-stats.p.rapidapi.com",
      "X-RapidAPI-Key": "*******************************",
      "platform": "chrome",
      "User-Agent": "axios/1.4.0",
      "Accept-Encoding": "gzip, compress, deflate, br"
    },
    "method": "get",
    "url": "https://chrome-stats.p.rapidapi.com/api/detail?id=gnkndpcagheiihcmllkdiadioglnonoj"
  },
  "code": "ERR_BAD_REQUEST",
  "status": 429
}
Rapid account: Admin Qo Wnih Uxr
admin-QoWnihUxr Commented 10 months ago

Hi Shai,

Do you have a sample response (including the response headers) when the 429 error occurred? I checked RapidAPI analytics dashboard and could not find any 429 error there. Having some extra information like a sample request+response and the approximate time when it occurred would be very helpful.

Thanks,
Hao

ディスカッションに参加しましょう-以下にコメントを追加してください:

ログイン/サインアップして新しいコメントを投稿