How to Use Integrations, API Keys, and Webhooks in LiveClass

LiveClass integrations help you connect sessions and workflows with other tools using ready-made apps, API keys, webhooks, automation tools, and embed options. This guide explains what each option does and how to configure API keys and webhooks securely.

Who this is for: Account administrators and developers

Understanding the Integrations Tabs

Go to 'Integrations' in LiveClass to access the available options.

API keys and webhooks are available on selected plans. If you see an upgrade notice, check your plan under 'Plans & billing'.

Creating and Managing API Keys

API keys authenticate requests made to the LiveClass API.

Step 1: Access Integrations

Go to 'Integrations' → 'API keys'.

Step 2: Create an API Key

Click '+ Generate key'.

Step 3: Keep Your API Keys Secure

'Copy' the full key immediately and store it securely.

Follow these security practices:

• Store keys in your application's secret manager or other secure server-side configuration.

• Never commit keys to source control or expose them in front-end code.

• Use separate keys for different systems so you can revoke one integration without affecting others.

Anything included in browser-side code can be accessed by people using that browser.

Step 4: Rotate an API Key

Use the 'Rotate' button to rotate your API key.

Setting Up Webhooks

Webhooks notify your system when selected events occur in LiveClass, such as a session starting or a recording becoming available. They let your application react to events without repeatedly checking the API.

Step 1: Create a Webhook

Go to 'Integrations' → 'Webhooks'. Select '+ Create Webhook'.

Step 2: Enter Webhook Details

Enter the 'Webhook URL' where LiveClass should send event notifications. Select the 'Events' your application needs to receive and click 'Create' to save the webhook.

Step 2: Configure Your Webhook Endpoint

Your receiving endpoint should follow these practices:

• Respond quickly: Acknowledge the webhook promptly and process time-consuming tasks in the background.

• Handle duplicate events: The same event may arrive more than once. Make processing idempotent so repeated deliveries do not create duplicate records or actions.

• Allow for out-of-order events: Do not assume events always arrive in the order they occurred.

• Verify incoming requests: Confirm that a webhook genuinely came from LiveClass before acting on its payload. Follow the supported verification method and treat the payload as data, not instructions.

Step 3: Troubleshoot Webhook Failures

If a webhook stops working, check the following in order:

1. Confirm the destination URL is correct and reachable.

2. Verify that the endpoint returns a successful response.

3. Check that the endpoint responds quickly enough.

4. Confirm that the webhook is still subscribed to the required events.

A changed or outdated destination URL is a common cause of delivery failures.

Using Automation Tools

The What you can automate tab lists supported triggers and actions for automation tools such as Zapier.

Automation tools can help you connect LiveClass to other applications without building a custom integration. For example, you can automate workflows that update a CRM record, add session information to a spreadsheet, or send a notification to a chat tool.

To get started, open the automation tab and review the available triggers and actions for your workflow.

Embedding LiveClass in an LMS

LiveClass supports a server-side launch flow for integrating hosted sessions into a learning management system (LMS).

1. Keep your LiveClass API key on your server.

2. From the LMS backend, send a POST request to /api/launch with the external user's details and session or context information.

3. Open the returned joinPath in the LiveClass app, normally through top-level navigation or a new browser window.

4. Use the short-lived launchId returned by the server launch request for the hosted browser join. Never expose the API key in browser JavaScript.

Important: The standard launch flow opens the hosted LiveClass experience; it is not an iframe integration. Live sessions reject third-party iframes because the media interface and security headers require a top-level browsing context.

If you need to embed a session in an iframe, use the explicitly configured, origin-allowlisted Embed integration. Do not disable frame protection globally to work around embedding restrictions.

Frequently Asked Questions

I lost my API key. Can I retrieve it?

No. Create a new key, update your integration, and delete the old key.

Can I restrict what an API key can do?

Keys act on behalf of your account. Use separate keys for different systems so you can revoke them independently.

Why did my webhook fire twice for the same event?

Webhook events can be delivered more than once. Make your endpoint idempotent by checking whether an event has already been processed before acting on it.

Do I need both webhooks and an API key?

Not always. Use whichever capability your integration requires. You need both only when your workflow needs to send requests to LiveClass and receive event notifications.

Why do the API keys or Webhooks tabs show an upgrade notice?

These features are available on selected plans. Check Plans & billing to review your plan's inclusions.

LiveClass integrations let you connect your account to external applications, automate workflows, and build custom API-based connections. Choose the appropriate integration method, keep credentials secure, and configure webhooks to handle duplicate or delayed events reliably.