When developing an ApiRTC application, you meet the following concepts.


Your account on ApiRTC platform consists in a main Enterprise and an admin User.


An Enterprise is an entity associated to your account.

ApiRTC allows to create children Enterprises to the main Enterprise, each one having it's own apiKey. This is useful to isolate quota and billing of different projects.

Enterprises management car be done through the ApiRTC dashboard open_in_new.


One apiKey is associated to one Enterprise. The apiKey is a simple string that identifies a client application without any principal. It is useful for accessing the API, associating ApiRTC usage with your project for quota and billing.


ApiRTC let's you decide wether the users of your application are managed by your backend or by ApiRTC user management.

Each Enterprise has at least one User which is an administrator. But you can create more and authenticate them from your client application.

Users management car be done through the ApiRTC dashboard open_in_new, or can be provisioned programmatically though the ApiRTC REST API.


A Conversation is the way to make individuals communicate with each other.

ApiRTC enables chat, watch, listen and/or share real-time audio, video, data, screen, and many associated features to help sharing information.


Usage based

ApiRTC billing is based on usage.

Video Conversation billing is based on the number of minutes in communication and per participant.

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.