Rate Limits

This page explains how rate limiting works in SERP and how to retrieve your current account limits.

Rate limits help ensure platform stability and consistent performance for all customers.

SERP uses two types of limits:

  • Requests Per Second (RPS)

  • Concurrent Requests

Both limits are enforced simultaneously.


Requests Per Second (RPS)

Requests Per Second (RPS)

The RPS limit controls how many new requests you can send each second.

Example

If your account has an RPS limit of 20:

  • Sending 10 requests in one second is allowed.

  • Sending 20 requests in one second is allowed.

  • Sending more than 20 requests in one second may result in some requests being rate limited.


Concurrent Requests

The Concurrent Request limit controls how many of your requests can be processing at the same time.

Because SERP requests may take several seconds to complete, Concurrent Request limits are often reached before RPS limits.

Example

If your account has a Concurrent Request limit of 400:

  • If 100 of your requests are currently processing, you can continue sending additional requests.

  • If 250 of your requests are currently processing, you can continue sending additional requests.

  • If you already have 400 requests processing simultaneously, additional requests may be rate limited until existing requests complete.


How Limits Are Applied

Both limits are enforced simultaneously.

A request may be rate limited if:

  • You exceed your configured RPS limit

  • You exceed your configured Concurrent Request limit.

For a request to be accepted, it must be within both limits.


Retrieve Your Current Limits

You can retrieve your account's configured limits using the Rate Limit endpoint.

Endpoint

Authentication

Use HTTP Basic Authentication:

Where <base64(username:password)> is the Base64-encoded string of your NetNut credentials.


Example Response

Response Fields

Field
Description

rps_limit

Maximum requests per second allowed for your account.

concurrent_limit

Maximum number of requests that can be processed simultaneously for your account.

render.rps_limit

Maximum render requests per second allowed for your account.

render.concurrent_limit

Maximum number of render requests that can be processed simultaneously for your account.


Notes

  • Both RPS and Concurrent Request limits are enforced simultaneously.

  • Exceeding either limit may result in requests being rate limited.

  • Limits are account-specific and may vary by package.

  • Both synchronous and asynchronous requests count toward your configured limits.

  • The Rate Limit endpoint returns your configured limits and does not return current usage.

Last updated