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
  • Billing
  • Usage-based
Edit on GitHub
  1. What is ApiRTC?

Billing

PreviousVintage Browsers CompatibilityNextProduct Roadmap and releases

Last updated 2 years ago

Billing

Usage-based

ApiRTC billing is based on usage in minutes x participant in the room.

  • Video audio communications are billed by the number of minutes in communication by the number of participants.

  • SMS are billed for each message sent.

  • SIP incoming calls are billed by the number of minutes

Per Enterprise

Organizing your communication traffic by use case is paramount to simplifying the billing allocation process. The concept of Enterprise allows developers to spin up new subaccounts for each new use case and business unit, allowing billing and traffic to be allocated efficiently at the end of every month.

Understand more about pricing:

ApiRTC pricing