Server API Overview

RC provides a set of server APIs and multiple server callbacks for real-time audio/video products (e.g., RTC calls, meetings, and low-latency live streaming), working alongside client SDK features to deliver comprehensive business solutions.

Feature Overview

Server APIs offer the following core functionalities:

1. User onboarding for RC services
   Your application server must call the User Registration API to exchange user IDs for Tokens. Clients require valid Tokens to connect to RC servers. See User Registration.

2. Advanced capabilities (optional based on business needs):

   • Banned User: Restrict misbehaving users from joining any room.
   • Stream Mixing: Combine multiple live streams into one for enriched viewing.
   • Third-party CDN Relay: Improve content delivery efficiency.
   • Cloud Recording (value-added service): Record sessions for playback/archiving.
   • Content Moderation (value-added service): Ensure compliance with real-time review.

3. Audio/Video callbacks:

   • Room Status Update Callback: Sync room state changes to your endpoint.
   • CDN Streaming Callback: Track third-party CDN push status.
   • Cloud Recording Status Callback: Monitor recording tasks (requires Cloud Recording API).
   • Cloud Player Status Callback: Track playback status (requires Cloud Player API).
   • Content Moderation Result Callback: Receive violation event alerts and task status.

Important Notes

Critical

• The User Registration API is mandatory—without it, RC cannot serve your app users.
• Never call Server APIs directly from client-side. Always route through your application server to prevent App Secret leaks.
• Avoid KeepAlive for API calls. If necessary:
  • Set idle timeout <55 seconds per connection.
  • Recycle connections after 80 reuses.
    Pro tip: Rotate connections after 55s idle or 80 reuses to maintain load balancing.