Connect your deployment to what you already run

A bots API that takes one request, webhooks configured in the console, and meetings embedded in your own portal. All of it over a path you control.

Talk to usSee bots and automations
  • Bots API
  • Webhooks
  • Embedded meetings
  • One ApiKey header
  • Certificate pinning

Built to plug in

Bots

Post text, media, files, and links into a chat with a single request, and read replies back with a cursor. Create a bot in the admin console, put its key in one header, and that is the entire integration for most systems. Delete the bot to revoke access.

Webhooks

Configure webhooks in the admin console and your deployment calls your endpoints when events happen. No code runs inside the platform; your system decides what to do with each event.

Embedded meetings

Open meetings from inside your own portal through a standard OAuth-style auth-code flow. A direct variant serves systems that can hold a secret, and a redirect variant serves browser-only portals.

Certificate pinning

The mobile app trusts only your deployment's certificate, so integrations run over a path you control.

One request is the whole integration

Create a bot in the admin console and you get an API key. Put it in a single header and post text, media, files, or links to a chat. Read a chat with a cursor to pick up what people replied, and answer in the same chat. Revoke the whole thing by deleting the bot.

  • One ApiKey header, no token exchange
  • Post text, media, files, and links
  • Read chats with a cursor and reply two ways
  • Delete the bot to revoke access
POST /api/bot/messages
Content-Type: application/json
ApiKey: <your-bot-key>

{
  "text": "Deploy finished, all checks passed"
}

One header, one body. Media, files, and links post the same way.

Meetings inside your own portal

A standard auth-code flow in three steps.

  1. 1

    Your portal requests a code

    Your system asks your deployment for an auth code on behalf of the signed-in user. Systems with a backend use the direct variant; browser-only portals use the redirect variant.

  2. 2

    The user approves

    The user confirms once that your portal may open meetings for them. Your users stay in the tool they already use.

  3. 3

    The meeting opens inside your portal

    The code is exchanged and the meeting opens embedded in your page. People join from there without leaving.

Tell us what you want to connect.

Describe the system and the workflow, and we will show you the bot, webhook, or embedded meeting that fits it.

Talk to usTry the showcase app