Skip to main content
Best answer

Pinterest you have exceeded your rate limit

  • November 2, 2020
  • 2 replies
  • 6915 views

Im trying to connect my bigcartel shop and pinterest. When i go to connect my pinterest it says you have exceeded your rate limit and to try again in a few minutes. How do I fix this?

Best answer by jesse

Hey @daffyshawtie12! To borrow a response from our support team:

Looks like Pinterest is giving us the authentication error because of a rate-limiting issue. Pinterest has enacted strict limits to the number of times each day that we can make requests to their systems for new data. Whenever the limit is reached, they will return these error messages. There isn't much we can do about this as the limits have been set from their end.

This change can also be found here on Pinterest’s developer doc: https://developers.pinterest.com/docs/api/overview/?#rate-limiting

Hope that helps to clear things up! Using a Delay after Queue step within your Zap like Troy mentioned may be a helpful workaround to try. 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34070 replies
  • November 2, 2020

Try adding a Delay after Queue step to your Zaps.


jesse
Forum|alt.badge.img+9
  • Architect
  • 1348 replies
  • Answer
  • January 6, 2021

Hey @daffyshawtie12! To borrow a response from our support team:

Looks like Pinterest is giving us the authentication error because of a rate-limiting issue. Pinterest has enacted strict limits to the number of times each day that we can make requests to their systems for new data. Whenever the limit is reached, they will return these error messages. There isn't much we can do about this as the limits have been set from their end.

This change can also be found here on Pinterest’s developer doc: https://developers.pinterest.com/docs/api/overview/?#rate-limiting

Hope that helps to clear things up! Using a Delay after Queue step within your Zap like Troy mentioned may be a helpful workaround to try.