Skip to main content
Here’s a polished version that matches the style of the rest of your documentation.

​
Rate Limits

The SERPtag REST API uses rate limits to ensure reliable performance and fair usage for all users. Every API key has its own hourly request allowance. Most applications will never reach the limit during normal use.

​
Requests Per Hour

Each API key includes the following request limit. The request counter automatically resets at the beginning of each clock hour (for example, 2:00 PM, 3:00 PM, 4:00 PM, and so on).

​
What Counts as a Request?

Every authenticated GET request made to the SERPtag REST API counts as one request. For example:
  • GET /projects/ → 1 request
  • GET /project-keywords-list/123/ → 1 request
  • GET /keyworddata/456/ → 1 request
  • Each paginated request using limit and offset → 1 request
If you’re using the SERPtag MCP Server, tool calls that retrieve data from the REST API also count towards the same hourly limit.

​
What Happens If You Reach the Limit?

If your API key exceeds the hourly limit, the server will return a 429 Too Many Requests response. Example response:
Once the hourly limit resets, you can continue making requests immediately.

​
How to Reduce API Usage

If your application makes a large number of requests, consider the following recommendations.
  • Cache project and keyword data whenever possible.
  • Use pagination (limit and offset) instead of requesting everything repeatedly.
  • Batch reporting jobs instead of making individual requests for every keyword.
  • Avoid continuously polling the same endpoint.
  • Implement automatic retry logic when a 429 response is received.
Following these practices will improve performance while reducing unnecessary API traffic.

​
Other Usage Limits

Your SERPtag subscription also determines how much data your account can access. The REST API only returns data that belongs to your account and within the limits of your current subscription.

​
Best Practices

For the best experience with the SERPtag REST API, we recommend:
  • Cache responses whenever possible.
  • Retrieve project IDs before requesting keyword data.
  • Use pagination for large keyword lists.
  • Respect rate limits and avoid unnecessary requests.
  • Handle 429 Too Many Requests responses gracefully with exponential backoff or retry logic.

​
Need Higher Limits?

If your application requires a higher request allowance or you’re building a large-scale integration, we’d be happy to help. Please contact our team to discuss your requirements. Email: support@serptag.com

​
Related Documentation

Continue exploring the REST API:
  • Authentication — Learn how to authenticate every request.
  • Endpoints — Browse every available REST API endpoint.
  • Error Codes — Understand common API responses and troubleshooting.