What Are the Feedspace API Rate Limits?

Overview

Feedspace enforces rate limits on all API requests to protect platform stability and ensure consistent performance for every user. Understanding these limits helps you build integrations that stay within the allowed thresholds and handle errors gracefully when limits are reached.

Standard Rate Limits

The standard rate limit for the Feedspace REST API is 60 requests per minute per API key. This limit applies across all endpoints and resets every 60 seconds.

Rate limits may vary depending on your plan. Check the official Feedspace API documentation for the current limits that apply to your account.

HTTP 429: Too Many Requests

When your integration exceeds the rate limit, the Feedspace API returns an HTTP 429 Too Many Requests response. The response body includes an error message indicating the limit has been reached. Your application should detect this status code and pause before retrying.

Example 429 Response

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Please slow down and try again."
}

Best Practices for Staying Within Limits

Implement Exponential Backoff

When your application receives a 429 response, do not retry the request immediately. Instead, use exponential backoff: wait a short delay before the first retry, then double the delay for each subsequent attempt. This approach reduces load on the API and gives the rate limit window time to reset.

A simple exponential backoff pattern:

1. Receive a 429 response.
2. Wait 1 second, then retry.
3. If still receiving 429, wait 2 seconds, then retry.
4. Continue doubling the wait time (4 s, 8 s, 16 s) up to a reasonable maximum before surfacing an error to the user.

Cache GET Responses

Avoid fetching the same data from the Feedspace API on every page load or user action. Instead, cache the responses from GET requests on your server and serve the cached data to your frontend. Set a cache duration appropriate to how frequently the data changes, for example, 5 to 15 minutes for review lists. Caching significantly reduces the number of API calls your integration makes and keeps you well within the rate limit.

Use Webhooks Instead of Polling

If you are repeatedly calling the API to check whether new reviews have arrived, switch to Feedspace Webhooks instead. Webhooks push data to your endpoint the moment a new review is submitted, eliminating the need to poll the API at regular intervals. This keeps your request count low and ensures your application receives updates in real time without consuming rate limit quota unnecessarily.

Batch Operations Where Possible

Where the API supports it, retrieve multiple records in a single request rather than making one request per record. Fetching a paginated list of reviews in one call is far more efficient than looping through individual review IDs one at a time.

Plan-Based Limits

Rate limits may differ between Feedspace plans. Higher-tier plans may allow a greater number of requests per minute to support larger integrations and higher-volume use cases. For the exact limits that apply to your current plan, refer to the official Feedspace API documentation at docs.feedspace.io.

Frequently Asked Questions

Does the rate limit apply per API key or per workspace?

The rate limit is enforced per API key. Each workspace has its own API key, so the limit is effectively per workspace as well.

Does the rate limit reset automatically?

Yes. The request counter resets every 60 seconds. Once the current window expires, your API key can make the full number of allowed requests again.

Will I be notified before hitting the limit?

No advance warning is sent. Your application must handle the 429 status code proactively by checking every response and implementing backoff logic.