Skip to main content
The server API is called by your backend.

Basic usage

Use the server endpoints that fit your business needs to control your meetings.

Calling conventions

  1. Request method: POST
  2. Request format: application/json, encoded in UTF-8
  3. Base URL: https://{server-domain-or-IP}/meeting/{endpoint-path}
  4. Request headers
  1. Signing algorithm
  • Step 1: Build the string to sign by joining the app ID, nonce, timestamp, and the JSON string of the request body with &
The field names in the string to sign must match the request header names you actually send. You can use any of the three header names, but whichever you pick, the string to sign must start with that name—sending an app_id header while signing appid=... fails authentication.
Also, sign the request body as the raw string. It must be byte-for-byte identical to what you send (including whitespace and field order); don’t serialize it again.
  • Step 2: Compute HMAC-SHA256 over the string. The key is the appkey secret key.
  • Step 3: Convert the binary result to lowercase hexadecimal to get the signature
  1. Response format: JSON