Roam HQ API

Name: Roam HQ API
Brand: Roam HQ API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar Schedulingbearer5 EndpointsREST

For Agents

Programmatically send a roam message, list groups. Covers 5 operations with bearer authentication.

Use for: I need to send a roam message, I want to groups, Search for meeting recordings, Find all export message events

Install Jentic One Beta

Connect the Roam HQ API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Roam HQ 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 Roam HQ API.

Send a Roam message

List groups

Export message events

Test endpoint

GET STARTED

Start building with Roam HQ API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Roam HQ API for, with concrete tasks.

★ Productivity Operations

Use the Roam HQ API to perform productivity operations programmatically. The API provides 5 endpoints covering core functionality including send a roam message, list groups, list meeting recordings.

Call POST /chat.sendMessage to send a roam message

Automated chat.sendMessage Management

Automate chat.sendmessage operations by combining multiple Roam HQ API endpoints. Agents can list groups and then list meeting recordings in a single workflow.

Call GET /groups.list to list groups, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Roam HQ 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 'send a roam message', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — the roam hq api is your programmatic interface to your all-in-one virtual office.

METHOD

PATH

DESCRIPTION

POST

/chat.sendMessage

Send a Roam message

GET

/groups.list

List groups

GET

/recording.list

List meeting recordings

POST

/messageevent.export

Export message events

GET

/test

Test endpoint

POST

/chat.sendMessage

Send a Roam message

GET

/groups.list

List groups

GET

/recording.list

List meeting recordings

POST

/messageevent.export

Export message events

GET

/test

Test endpoint

Why Jentic?

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

Credential isolation

Roam HQ 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., 'send a roam message') and Jentic returns the matching Roam HQ API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

FAQs

Specific to using Roam HQ API through Jentic.

What authentication does the Roam HQ API use?

The Roam HQ 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 send a roam message with the Roam HQ API?

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

What are the rate limits for the Roam HQ 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 send a roam message through Jentic?

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

How many endpoints does the Roam HQ API have?

The Roam HQ API exposes 5 endpoints covering chat.sendmessage, groups.list, messageevent.export operations.

Roam HQ API

Connect the Roam HQ API to your agent

Capabilities

Start building with Roam HQ API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs