Skip to main content
QriibQriib
DevKit / APIs & SDKs

Build room and session workflows into your application.

APIs define the service contract for rooms, access and session data. SDKs provide language-specific clients or mobile meeting tools to implement that contract in your chosen environment.

Open DevKit dashboardRead the integration guide

Keep the trust boundary clear.

  1. Your client

    User interface and participant handoff.

  2. Trusted backend

    Authorization and request signing. Organization and project secrets stay here, never in browser or mobile code.

  3. DevKit services

    Room creation, participant access and session resources through the documented API contract.

Connect the session lifecycle.

Select the documented operations your workflow needs and verify access against your deployment.

Rooms and sessions

Create quick or scheduled audio and video rooms and manage session status.

Read room reference

Projects and branding

Configure projects and use project credentials for supported branding workflows.

Read project reference

Webhooks

Configure destinations for room, participant, recording and analytics events.

Read webhook guide

Access and invitations

Authorize participant entry and review protected invitation creation, redemption and revocation.

Read access reference

Choose your implementation tool.

TypeScript / JavaScript and Python provide server-side API clients. Flutter / Dart provides mobile meeting tooling. Check each package's requirements and coverage.

Server-side API orchestration

Typed client with documented room, recording, analytics and branding helpers, request signing and named errors.

SDK package
@vconnct/devkit
Documented environment
Node.js 18+

Install

npm install @vconnct/devkit

Browser compatibility does not make shared secrets safe in browsers. Use a trusted backend and verify coverage of newer endpoints.

Read SDK guideView package

From configuration to a tested workflow.

  1. Configure your project

    Set up credentials and confirm the environment, API version and enabled capabilities. V5 Gateway availability depends on configuration; it is not a universal V4 replacement.

    Review configuration

  2. Sign on a trusted server

    Validate request signing against your deployed contract and authorize participant handoff from your backend.

    Review authentication

  3. Integrate and test

    Connect creation, entry and session follow-up. Test errors, permissions and event handling before production use.

    Review event handling

Choose your billing path.

  • APIs: PAYG or eligible Wesal plans.
  • SDKs: PAYG.
  • LTI: eligible Wesal Pro or Business plans only.
View pricing & terms
    Build room and session workflows into your application. | Qriib