Skip to main content

Why am I being rate limited?

Amanda Cross
Updated

To protect system performance for all Ringba users, some parts of the application have rate limits. This article contains the following sections:

Logs and Reporting Limits

The following parts of the Ringba platform are subject to a rate limit:

  • Reporting Panel
  • Reporting Summary
  • Insights Tool
  • Exporting call details

The rate limit is:

  • 5 requests/second or 80 requests/minute

If you exceed the rate limit, the system returns an error message similar to this:

rate_limit_error.png

The message (Your account has been rate limited at the '[time]' for the resource '[resource name]') specifies whether you exceeded the per-second or per-minute limit. It also includes the name of the resource you requested too many times.

See the Reporting article for more details.

API

Get Details about Specific Calls

You can also use the API to get details about specific calls. See Get Details About Specific Calls. This API endpoint is also has a rate limit:

  • 200 requests/minute

This limit applies to all users in your account, across this screen and the related API requests. For example, you could have five admin users loading the Reporting screen at the same time, but if a Get Logs API request came in during the same second, it would fail.

Get RTB Bid Log

The /rtb/bid/{bid_id} endpoint, also called GetRTBBidLog, has a rate limit :

  • 150 requests/minute

If you exceed this limit, you receive a message like the following:

{'transactionId': 'TR931fc463-ca1b-42e5-88f8-fb99x9xxxxx9', 'isRateLimited': True, 'exceedingRateLimit': 'Minute', 'rateLimitedResource': 'GetRTBBidLog', 'message': "Your account has been rate limited at the 'Minute' for the resource 'GetRTBBidLog'", 'rateLimit': {'perMinute': {'limit': 150, 'currentCount': 302}}}

Call logs export rate limit

We have a limit of the number of times that the client can ping our API to get Call logs export. This applies for both UI, when they click to export the CSV, and also via API when they ping our endpoint to get call logs. The limit is per account, and it applies to all users. The limits are:

  • 20 requests/hour
  • 200 requests/day
  • 5 requests/minute

RTB Pings

To protect Ringba performance, we rate limit to prevent duplicate requests and avoid loops on RTB pings.

When Ringba receives a bid, it captures the combination of the following information and “locks” the bid while it is in process:

  • publisher RTB ID
  • caller ID
  • user tags

Ringba will not accept another bid with the same data while the original bid is locked. Once processing is complete, Ringba releases the lock. For example, if the bid takes 3 seconds to process, after 3 seconds you can send another bid with the same publisher RTB ID, caller ID, and user tags.

If you exceed this rate limit, the system returns this error message:

Code 1025: Ringba - Rate Limited

If you encounter this error, you can wait a few seconds and try again.

Note: Even though a campaign's Real Time Bidding tab contains a Rate Limits section, the fields in that section do NOT affect this rate limit. Do not change the Maximum Requests value to try to resolve this issue.

 

Related articles