Skip to main content

Server API Domain Names

When creating an application on RC, you can select either the China (Beijing) Data Center or global data center based on your business environment (see data center). Different data centers use independent server API addresses. Your application server must use the corresponding Server API address for each data center when making API calls; otherwise, requests will fail to return correct results.

Important
  • To prevent App Secret leakage and other security risks, all Server API interfaces must be called through your application server. Never call Server API interfaces directly from client-side code.
  • When calling Server APIs, we recommend avoiding KeepAlive connections. If KeepAlive is necessary for specific scenarios, ensure each persistent connection has an idle timeout below 55 seconds and is reused fewer than 80 times. We recommend establishing new connections after 55 seconds of idle time or 80 reuses. Prolonged use of the same connection may disrupt API load balancing and affect failover strategies.

Server API Domain Names​

China (Beijing) Data Center API Addresses​

RC provides two independent server API addresses for applications in the China (Beijing) data center:

  • api.rong-api.com
  • api-b.rong-api.com
Note

We recommend implementing automatic fallback logic between primary and secondary domains to minimize service disruptions caused by potential CDN provider issues that could affect RC Server API accessibility.

Global Data Center API Addresses​

For applications in global data centers, use the corresponding server API addresses:

  • Singapore: api.sg-light-api.com (primary), api-b.sg-light-api.com (secondary)
  • Singapore B: api.sg-b-light-api.com (primary), api-b.sg-b-light-api.com (secondary)
  • North America: api.us-light-api.com (primary), api-b.us-light-api.com (secondary)
  • Saudi Arabia: api.sau-light-api.com (primary), api-b.sau-light-api.com (secondary)
Important
  • Always verify domain names in the App Key page of the Console.
  • Applications using global data centers must also configure client SDK data center addresses. See the knowledge base article RC Global Data Center Usage Guide.

Best Practices for Domain Fallback​

Using a single Server API address may cause access latency due to CDN provider issues, potentially impacting business operations. We recommend implementing the following domain fallback logic:

  1. Maintain the currently used domain when calling RC Server APIs.

  2. If timeout or unavailability occurs during API calls, immediately switch to the secondary domain and update the current domain record. This cyclic approach minimizes business impact.

Last updated on