Whereby REST API

Name: Whereby REST API
Brand: Whereby REST API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer27 EndpointsREST

For Agents

Programmatically create meeting, get meetings. Covers 27 operations with bearer authentication.

Use for: I need to meeting, I want to meetings, Search for meeting, Find all meeting

Install Jentic One Beta

Connect the Whereby REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Whereby REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Whereby REST API.

Create meeting

Get meetings

Delete meeting

Query and filter Whereby REST API records by parameters

GET STARTED

Start building with Whereby REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Whereby REST API for, with concrete tasks.

★ Developer Tools Operations

Use the Whereby REST API to perform developer tools operations programmatically. The API provides 27 endpoints covering core functionality including create meeting, get meetings, get meeting.

Call POST /meetings to create meeting

Automated Insights Management

Automate insights operations by combining multiple Whereby REST API endpoints. Agents can get meetings and then get meeting in a single workflow.

Call GET /meetings to get meetings, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Whereby REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'create meeting', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

27 endpoints — these are the reference docs for the whereby rest api.

METHOD

PATH

DESCRIPTION

POST

/meetings

Create meeting

GET

/meetings

Get meetings

GET

/meetings/{meetingId}

Get meeting

DELETE

/meetings/{meetingId}

Delete meeting

GET

/recordings

Get recordings

GET

/recordings/{recordingId}

Get recording

DELETE

/recordings/{recordingId}

Delete recording

GET

/recordings/{recordingId}/access-link

Get recording access link

POST

/meetings

Create meeting

GET

/meetings

Get meetings

GET

/meetings/{meetingId}

Get meeting

DELETE

/meetings/{meetingId}

Delete meeting

GET

/recordings

Get recordings

GET

/recordings/{recordingId}

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Whereby REST API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create meeting') and Jentic returns the matching Whereby REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Whereby REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Whereby REST API through Jentic.

What authentication does the Whereby REST API use?

The Whereby REST API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create meeting with the Whereby REST API?

Yes. Use the POST /meetings endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Whereby REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create meeting through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create meeting'. Jentic returns the matching Whereby REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Whereby REST API have?

The Whereby REST API exposes 27 endpoints covering insights, meetings, recordings operations.