API Rate Limits

Hootsuite enforces API rate limits for its REST APIs. Rate limit configuration consists of a daily usage quota and per second request limit. Limits are set to 20 requests / second to a maximum daily quota of 100,000 calls per day.

We return rate limit and quota headers in our API responses to allow clients to monitor their API usage.

Header Name
Description

X-Account-Quota

A description of the quota applied to the client's account.

X-Account-Quota-Used

The number of calls that have been made against the account quota.

X-Account-Rate-Limit-Requests-Remaining

Rate limits are applied per second. This value is the remaining number of requests the client can make within the current rate limit window.

Note: The remaining requests value is returned on a per node basis, so should only be used as a guide. The rate limit allowance is divided equally across all the nodes in the cluster.

Example response header

Connection →keep-alive
Content-Encoding →gzip
Content-Length →385
Content-Type →application/json;charset=UTF-8
Date →Fri, 19 May 2017 21:46:07 GMT
Server →nginx/1.8.0
X-Account-Quota →100000 per day
X-Account-Quota-Used →6
X-Account-Rate-Limit-Requests-Remaining →14

If you exceed your daily quota or rate limit allowance your request will be rejected. An HTTP 429 (Too Many Requests)​ response will be returned. Clients must back off until the end of the current rate limit window before making any more requests.

Example response body for throttled request

{
  "errors": [
    {
      "code": 1003,
      "message": "Account plan limit exceeded",
      "id": "0000015bd565ee00-8fbd"
    }
  ]
}

We reserve the right to rate limit other functionality to prevent abuse, spam, denial-of-service attacks, or other security issues. Where possible we'll return a descriptive error message, but the nature of this type of rate limiting often prevents us from providing more information.

API Rate Limits


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.