Dear Wix Community & Team,
I have been using the official NPM package from Wix to programmatically manage feeds in Wix Groups (Post, List, Update, Delete).
However, after a certain number of successful posts sequentially, I would be hit with a 403 Forbidden error, which I understand may be caused by throttling at Wix Backend. Previously, in the documentation, I understand the API rate limit to be 200 request per minute, but even when sending less than 200 req/min, the 403 Forbidden error would still appear. I also note that this is not the 429 Throttled error.
May I ask if the rate limit has changed, and if so, what might the new rate limit be?
Thanks all!
Ref:
NPM Package: https://www.npmjs.com/package/@wix/wix-groups-feed-client
API Rate Limits: https://dev.wix.com/docs/rest/articles/get-started/rate-limits
403 is a permission error. I’d look into that side of it more.
I cant find any documentation that says limits are different
Hi there @Dan_Suhr ,
Thanks for the prompt response. And yes, fully understand that the 403 (Forbidden) is a permission error vs. the 429 (throttled error).
That said, the code I ran works where the “[HTTP] response statusText: OK” until the 80-90th request where the “[HTTP] response statusText: Forbidden”. My suspicion is that on the Wix backend, the res should be sent as a 429 throttled error, but 403 Forbidden was mistakenly sent instead.
I have also tried multiple sequential job scheduling with backoff delays for retries but to no avail as well.
Hence am hoping Wix might be able to clarify what the exact API limits might be so that I can phase my HTTP req appropriately.
ok my suspicion is that there could be a secondary “burst” or per-second cap (or internal protection measure) that’s being triggered when many requests are made closely together, or that after many requests some token or header becomes invalid or gets dropped.
I recommend logging all requests & responses (with timing), pacing your requests more conservatively, testing read operations separately, and then raising a support case with Wix including those logs so they can check their backend rule for your API key / site.
Hi @Dan_Suhr ,
Thanks and great suggestions. I concur with your suspicions that Wix has some internal server-side protection measure being triggered. Or there might be a chance tokens / header gets invalid after a certain time.
For this community’s information, I was told by Wix that t here is a “throttling limit on creating posts in a group within a certain time frame (both per user and per IP).”, albeit it was not specified what those might be for me to build a conclusive workaround.
Nonetheless, I’m building a trial-and-error workaround using scheduled jobs to pace the API call. One I land on a successful number (frequency x batch size), I’ll drop everyone an update here so that you guys using similar API calls won’t have to start from the dark. =)
Keep you guys posted as well if Wix replies me on the API limit!
Cheers!