ApiRTC
BlogSupportSign UpConsole
  • ApiRTC Developer Portal
  • Status Page
  • What is ApiRTC?
    • Key Concepts
    • ApiRTC Architecture
    • Supported browsers
      • Vintage Browsers Compatibility
    • Billing
    • Product Roadmap and releases
  • Terms & Privacy Policies
    • 🍪Cookies
  • Get help & support
  • ApiRTC JS Library
    • QuickStart Guide
    • Where to find ApiRTC library?
    • Developers Guide
    • Video Communication LifeCycle
    • Demo App & Resources
    • Authentication
    • SDKs & Frameworks
      • ReactJS Libraries
        • Getting Started with ApiRTC React Hooks
        • ApiRTC React Hook Lib Reference
      • ReactNative library
      • Android SDK Reference
      • iOS SDK Reference
    • ApiRTC.js Reference
    • Changelog
  • REST APIs & Integration
    • Introduction
    • Apizee REST APIs
    • 3rd-party software integration
    • Webhooks
    • Rate Limits
    • Try it out
  • Other Resources
    • SDK License Agreement
    • ApiRTC Website
    • Blog
    • ApiRTC Community Github
Powered by GitBook
On this page
  • Overview
  • Rate Limit Policy
  • Response Headers
  • Handling Rate Limits
  • Best Practices
Edit on GitHub
  1. REST APIs & Integration

Rate Limits

Overview

To ensure optimal performance and fair usage of our API, we enforce rate limits on all API requests. These limits are in place to prevent abuse and to ensure that all users have equitable access to our services.

Rate Limit Policy

Our API allows up to 10 requests per minute per user. Exceeding this limit will result in rate limiting, preventing further requests until the time window resets.

Limit Details

  • Rate Limit: 10 requests per minute

  • Scope: Per user, across all endpoints

Response Headers

When making API requests, you can monitor your current rate limit status via the following response headers:

  • X-RateLimit-Reset: Time in seconds until the rate limit resets

Example Response Headers

X-RateLimit-Reset: 45

Handling Rate Limits

If the rate limit is exceeded, the API will return an HTTP 429 Too Many Requests status code.

Example 429 Response

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

{
  "error": "You have reached the maximum number of attempts. Please retry later."
}

Best Practices

To avoid hitting rate limits:

  • Implement exponential backoff in your retry logic.

  • Optimize API calls to reduce redundancy.

  • Cache responses where applicable to minimize repeated requests.

  • Monitor the X-RateLimit-Remaining header to adjust request frequency dynamically.

PreviousWebhooksNextSDK License Agreement

Last updated 2 months ago