Our API plans are designed to accommodate a wide range of applications, whether you're just starting out or scaling rapidly. Below, we've outlined important information regarding rate limits and monthly usage allowances.

Rate Limits

Our standard rate limiting is set to 5 requests per second. Based on our observations, this rate limit can accommodate up to 25 users concurrently on your website or app, as they don't all make requests simultaneously.

If your application requires higher throughput, this rate limit can be increased. However, we would first ensure that your application uses best practices for security. For more information, refer to the following help article: Best Practices For Securing Your Application

User-Specific vs. Account-Level Rate Limiting

When our firewall is properly implemented, we enforce user-specific rate limiting rather than account-level rate limiting. This is a significant advantage for your application:

• With account-level rate limiting: If any single user (or bot) abuses the API, your entire account gets penalized and all legitimate users of your application are affected
• With user-specific rate limiting: Only the specific user making excessive requests is throttled, while all other users continue to access your application normally

This approach protects your application from being disrupted by a single abusive user or bot, ensuring a better experience for your legitimate users. It also allows you to scale to higher usage levels more efficiently, since increased traffic from legitimate users won't trigger account-wide throttling.

Monthly Usage

All of our plans include 1 million requests per month. If you exceed this limit, don't worry—your API key will continue working. Instead of halting service, you'll simply be billed for the overage at a linear rate.

Example: If your subscription is $199 per month and you exceed 1 million requests by 1,000 requests, you will be billed 19.9 cents:

Overage cost = 1,000,000 / 199 × 1,000 = 19.9 cents

Overages are calculated in real-time, so you'll be billed in the following month for any extra requests.

What Counts as an API Request?

Any request made to our API counts toward your monthly limit, regardless of which endpoint is used. This includes requests to all available services such as MLS board data, Property Estimates, Local Insights, and any other add-ons.

How Monthly Limits Are Calculated

Your monthly request allowance is calculated per MLS board you have access to. For example:

• If you have access to 1 MLS board: 1 million requests per month
• If you have access to 3 MLS boards: 3 million requests per month
• If you have access to 5 MLS boards: 5 million requests per month

This applies to all add-ons and services—the limit scales with the number of MLS boards in your subscription.

Estimating Your API Usage

One million API requests typically supports approximately 25,000 monthly users when our firewall is properly implemented (see Best Practices For Securing Your Application).

Implementing the firewall is crucial because it:

• Drastically reduces unwanted bot traffic that would otherwise consume your API quota
• Allows friendly bots (like search engines) to continue accessing your site
• Provides more accurate usage metrics for real user traffic

Without the firewall, bot traffic can consume a significant portion of your monthly allowance, potentially affecting your application's ability to serve legitimate users.

Tracking Your Usage

You can monitor your API usage in real-time through our developer portal:

1. Log in at login.repliers.com
2. Click on the Usage tab to view your current usage statistics
3. Use the Live Tail feature to examine individual requests as they happen

This gives you complete visibility into your API consumption and helps you identify any unexpected usage patterns.

Need Higher Limits?

If your application is scaling and you need a higher monthly request limit or rate limit, get in touch with us. We're happy to review your requirements and discuss a custom plan that fits your needs.

What questions does this article answer?

• What are the default rate limits (requests per second) for Repliers APIs?
• Roughly how many concurrent users can my app support under standard limits?
• What are my monthly usage allowances and how are they measured?
• What happens if my app exceeds the included usage or rate limits?
• How can I increase my limits or discuss higher-volume use cases?
• What are the default rate limits for Repliers API usage (requests per second)?
• How are overage charges calculated in practice, with an example?
• Can I request higher rate limits or monthly quotas?
• Why should I review security best practices before increasing limits?

Updated on: 05/12/2025