I’m restarting this thread in regards to the continuing issue that was previously reported by other users, but the original thread appears to have been closed due to inactivity. I’m currently encountering the same problem receiving an “Exceeded daily rate limit” error.
I’ve already contacted Etsy support, and they confirmed that the API limit allows for up to 10,000 requests per 24-hour period and 10 queries per second. I’m well below those limits, and they confirmed that the issue is not originating from Etsy’s side.
I came across this thread and noticed it is still open, so I wanted to follow up here in hopes of finding a resolution. I would appreciate any help or guidance you can provide to resolve this persistent issue.
We are sorry for the disruptions caused by this issue. I’ve reached out to our devs, and here’s their response:
We’ve looked into this issue with our senior team, and we’re sorry to say we don’t have a workaround at this time. While personal OAuth credentials could bypass the 429 rate limit, we understand Etsy isn’t granting permissions for personal apps.
Etsy’s policies are beyond our control, and we’re unable to influence their decisions. We’ll keep an eye on the situation for any changes and apologize for the inconvenience.
Since i can configure my own token credentials what would i use as the callback URI for my OAuth config? I had https://www.make.com/oauth/cb/app but its being rejected. Anyone have an idea what the callback URI should be for the ETSY API Config?
No longer working today as well. I really don’t have 10000 requests per day. Seems that etsy is limiting direct make.com requests (i.e. all scenarios from all make users combined) and hitting the rate limit.
Problem with having your own app - it does not expose buyer_email property, which is essential for shipping to some countries. make.com integration would show it. Therefore alternative to use your own app with client secret is not possible
I wanted to weigh in here because we’ve been experiencing extremely frequent Etsy 429 / rate-limit errors via Make, and I believe that one of the key levers Make has (which doesn’t conflict with Etsy’s constraints) is monitoring and mitigating outlier users.
Since Etsy’s rate limits are out of Make’s control, the most realistic area Make can influence is how its user base behaves within the integration. Here’s what Make could do:
Monitor usage per user / per connection
Review the Etsy app usage logs (across all Make users) to detect any users or scenarios making unusually high request volumes.
Throttling or sandboxing for heavy users
If a given connection consistently spikes usage, throttle it (limit its calls), temporarily sandbox it, or isolate it so it doesn’t drag down everyone else.
Negotiate or shard the public app with Etsy
Make could approach Etsy about a partner-level arrangement: higher limits, or sharding — distributing users across multiple approved app credentials — so one user can’t knock out everyone else.
Best-practice guidance & usage caps
Encourage or enforce reasonable polling intervals, max calls per minute caps, and scenario setup optimizations for all users so that nobody inadvertently overloads the integration.
I truly understand that many constraints lie with Etsy’s API policies — this is not criticism but a push for Make to take what control it does have. Because right now, one user’s overuse is directly degrading service for many others.
If others here have log data (timestamps, volume spikes, etc.) or suggestions, I’d love to compare notes. Given how frequent these outages are getting, it would make a big difference if Make actively monitored and managed heavy users rather than assuming all users behave politely.
Thanks for reading — and thanks to Make staff or community moderators for keeping an eye on this and hopefully pushing it upward to your dev teams.
We’re truly sorry to hear that this issue has resurfaced, and we appreciate you bringing it up here in the community.
I just wanted to let you know that our development team has been notified and is looking into it. We’ll make sure to share any updates as soon as we have them.
We are very sorry for any trouble or disruptions this is causing.
Thank you so much for your patience and understanding.
Thank you for making the make.com dev team aware, although I have already raised this on a couple of occasions and received relevant replies.
For the benefit of other users, here is the reply from make.com cs/dev team:
As you mentioned, the rate limiting is handled directly by Etsy at the application level. Unfortunately, the usage data Etsy provides doesn’t include granular, per-user identifiers, which means we don’t have visibility into which individual accounts are consuming more of the shared quota. Because of this, we’re unable to reliably isolate or throttle specific users without unintentionally affecting others, as the rate limit information is aggregated before we receive the rejection responses.
That said, your suggestion is well noted — we’ll share this with our documentation and product teams so we can better communicate best practices and usage recommendations for the Etsy app. This should help users configure their integrations in a way that minimizes impact on the shared rate limits.
So, for the time being it doesn’t seem like there is a fix unless:
Etsy increase their global API limits / specific limits for make.com
Make/Etsy allow users to authenticate their integrations under separate API keys so every one has their own limits.
Just started using the etsy modules yesterday and made less than 100 calls in total and also getting hit by this rate limit. It makes it impossible to use.
We apologize for the frustration caused by this error.
Our devs have confirmed that they released a fix for this issue, and everything should be up and running now. Could you please check if your scenarios are working again?
Hi @Martin_Augustine, thanks for keeping us updated on the situation, and I’m really sorry to hear you’ve run into the same error again.
Could you please open a support ticket with our Customer Care team and share the details you mentioned here with them?
The Community doesn’t have access to your Make account, but Customer Care does. They’ll be able to troubleshoot the issue and guide you in the right direction.
