Sprout Public API Rate Limit Enforcement

The Sprout Public API lets your team pull Sprout data into your own data warehouses, dashboards, business tools and AI workflows. To keep the platform stable for all customers, the Sprout Public API began enforcing a rate limit of 60 requests per minute starting November 3, 2026.

Recommendations 

You can keep using the Sprout Public API for the same workflows as before, keeping in mind that requests are processed normally so long as they are under the threshold of 60 per minute for your account. 

To adjust your workflow to stay within the enforced limit, you can use the rate limit headers to see how much of your limit is left and build pacing into your integration. We recommend taking the following steps:

• Review your integration's request volume, especially scheduled jobs that send many requests at the same time. 
• Spread requests over time instead of sending large bursts. 
• If you get a ‘429 Too Many Requests’ response, pause before retrying.

For daily reporting pulls, one well-paced daily job is usually enough. Sprout data generally updates once a day, and most of the previous day's Analytics data is available by noon Central Time. Polling the last 7 days once a day captures late-arriving network data without repeated requests.

FAQs

Why am I suddenly getting 429 Too Many Requests errors from the Sprout Public API when my integration worked fine before?
As of November 3, 2026, the Sprout Public API consistently enforces its limit of 60 requests per minute across your whole Sprout account. Before this update, some integrations could go over that rate without getting errors. If your integration sends more than 60 requests in a minute, the extra requests now get a '429 Too Many Requests' response. To fix it, spread your requests out evenly over time instead of sending them in large bursts.

Is the Sprout Public API rate limit of 60 requests per minute counted per API token, per user, or for my whole Sprout account?
The limit applies to your Sprout account as a whole. 

How can I see how many Sprout Public API requests I have left before I hit the rate limit?
Sprout Public API responses now include rate limit headers that show how much of your limit is left. Your team can read these headers to pace requests and slow down before you reach the limit.

How do I avoid hitting the Sprout Public API rate limit when pulling Post Performance, Profile Performance, Messages, or Listening data?
Spread your requests evenly over time instead of sending many at once, and avoid starting several large jobs at the same moment. Sprout data generally updates once a day, so frequent re-polling doesn't usually return new data. For Analytics data, a daily pull after noon Central Time that covers the last 7 days captures most late-arriving network data. For Messages, filter on last_action_update_time to get only messages that changed since your last poll.

Does the Sprout Public API rate limit apply to Publishing, Cases, Listening, and Messages endpoints, or only to the Analytics reporting endpoints?
The rate limit applies to all Sprout Public API endpoints, including Analytics, Messages, Publishing, Cases, Listening, Media and Metadata. It is a single limit per customer, shared across all endpoints, so requests to any endpoint count toward the same per-minute allowance.

What should my integration do when the Sprout Public API returns a ‘429 Too Many Requests’ error, and how long should it wait before retrying?
Pause and retry the request. The limit refills continuously rather than resetting at the start of each minute – at 60 requests per minute you regain one request every second. Wait at least 1 second before retrying, and use exponential backoff with jitter (for example 1s, 2s, 4s, up to about 60s) if you keep receiving 429s. To avoid them altogether, check the X-RateLimit-Remaining header on each response and slow down as it approaches 0. Sending no more than one request per second keeps you within the limit.

Does the Sprout Public API rate limit enforcement apply to accounts hosted in Sprout's EU data center?
Yes. The change applies to accounts in both the US and EU data centers.

Do I need to change anything in my Sprout Public API integration before the rate limit is enforced?
If your integration already stays within 60 requests per minute, you don't need to change anything. If it regularly sends more than that, or sends large bursts at once, update it to spread requests out over time to avoid the '429 Too Many Requests' error.