Skip to content
OMeet
Talk to us

OMeet Developers

Build and integrate learning experiences with OMeet

Explore getting-started guides, API documentation, Sandbox and Console to connect OMeet with your institution’s learning platform or application.

Open SandboxRead Docs
View APIOpen Console

Four tools with four clear jobs

Docs explain the workflow, API provides technical reference, Sandbox supports testing, and Console manages your authorized scope.

Sandbox

Try integration flows in an authorized Workspace before connecting them to your system.

Open Sandbox

API

Look up operations, data, and authentication requirements in the API Reference.

View API Reference

Docs

Follow a guided path from accounts and Workspaces to testing and integration.

Read the guides

Console

Sign in to manage the Workspaces your account is authorized to access.

Open Console

A clear starting path

Get started in four steps

  1. 01

    Understand the integration

    Open Docs to learn how accounts, Workspaces, API and Sandbox fit together.

  2. 02

    Sign in and check access

    Open Console and confirm that you can access the Workspace you need.

  3. 03

    Try it in Sandbox

    Select a Workspace and run a scenario supported by the current interface.

  4. 04

    Connect your application

    Use the API Reference, keep server credentials in your backend, and handle documented results and errors.

Choose a path for your task

01

Prepare access and environment

Understand accounts, Workspaces, and how to open each tool.

02

Try a classroom workflow

Use an available Sandbox scenario to observe the process.

03

Connect from your backend

Keep server keys in the backend and follow the API Reference.

Frequently asked questions

01

Where should I start?

Read Docs, check your account and Workspace, then try a suitable flow in Sandbox.

02

How are Docs and API different?

Docs explain the process and starting points; API is the technical reference.

03

Do I need to sign in to use Sandbox?

The current Sandbox requires an account and an authorized Workspace; its service handles authentication.

04

What is Console for?

Console is the sign-in gateway for managing Workspaces your account is authorized to access.

05

Can I put an API key in frontend code?

Do not place server keys in browser code. Review the API’s specific authentication requirements first.

06

Is Sandbox always fully isolated?

Do not assume that. Read the environment information in the service and confirm the Workspace before creating test data.

Need to review a specific integration flow?

A technical discovery call is an additional support path; the tools and documentation remain directly accessible.

Discuss integration requirements