Clubhouse API

Name: Clubhouse API API
Brand: Clubhouse API
Availability: InStock

★ Only Publicly Available SpecSocial MediaSocial Managementnone41 EndpointsREST

For Agents

Drive the Clubhouse social audio app — sign in by phone number, manage follows and clubs, join channels, and read the events and topics feeds.

Quickstart

Get started with Clubhouse API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list upcoming clubhouse events"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Clubhouse API API.

Authenticate users via phone number (start, call, resend, and complete)

Look up user profiles, clubs, and topics by identifier

Join and leave audio channels and list available channels

Manage following relationships and inspect a user's follow graph

Send invites from a user's quota and surface waitlist follow-up actions

GET STARTED

Start building with Clubhouse API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Clubhouse API, keeping it validated and agent-ready.

The Clubhouse API is the unofficial integration surface for the Clubhouse social audio app, covering phone-number authentication, profiles, clubs, channels, topics, follows, invites, and event discovery. It exposes operations to start and complete phone-based sign-in, look up profiles and clubs, join and leave audio channels, manage follows, retrieve the upcoming events feed, and walk topic and follower graphs. The specification is reverse-engineered from public app traffic and is not maintained by Alpha Exploration Co.

Use Cases

Patterns agents use Clubhouse API API for, with concrete tasks.

★ Read-Only Social Listening on Clubhouse

Researchers and analysts who want to track activity on Clubhouse without scraping the app pull data through this API. /get_channels lists active channels, /get_events surfaces scheduled rooms, and /get_clubs_for_topic plus /get_users_for_topic walk the topic graph. Combined with /get_profile lookups for the users surfaced in those calls, this builds a social-listening dataset suitable for trend reporting on the audio platform.

Call /get_all_topics, then for each topic call /get_clubs_for_topic and aggregate the names of the top 10 clubs per topic

Personal Account Automation

Power users who want to script their own Clubhouse activity use the auth flow (/start_phone_number_auth, /complete_phone_number_auth) to obtain tokens, then call /follow, /update_username, and /update_notifications to manage their account. /get_online_friends returns who's available to chat on the homepage and /get_events lists upcoming rooms, which together drive a personal dashboard of Clubhouse state outside the app.

After completing phone number auth, call /follow with the target user_id then /me to verify the follow_count increased

Event and Room Discovery Aggregator

Teams building 'what's happening on Clubhouse' aggregator dashboards consume /get_events for the upcoming rooms list and /get_channels for currently live audio channels. Each event includes the host's profile information and the club it belongs to, and additional /get_profile and /get_club calls fill in colour for a content feed. The 41 endpoints cover the full read surface needed to render a Clubhouse-style discovery view.

Call /get_events and /get_channels and merge the results into a single feed sorted by start time and current listener count

AI Agent Browsing Clubhouse via Jentic

AI agents that build personal social briefings or media monitoring reports can call this Clubhouse API surface through Jentic to pull profile, club, and event data for a user. The agent expresses an intent like 'list upcoming events' or 'get a user profile', and Jentic loads the matching Clubhouse operation and returns structured JSON the agent can summarise without parsing screen-scraped content.

Through Jentic, search for 'list upcoming clubhouse events', load the clubhouseapi.com /get_events operation, and execute it to retrieve the next 24 hours of scheduled rooms

Key Endpoints

41 endpoints — the clubhouse api is the unofficial integration surface for the clubhouse social audio app, covering phone-number authentication, profiles, clubs, channels, topics, follows, invites, and event discovery.

METHOD

PATH

DESCRIPTION

POST

/start_phone_number_auth

Start phone number authentication

POST

/complete_phone_number_auth

Complete phone number authentication

POST

/me

Get the current user

POST

/get_profile

Look up a user profile by ID

GET

/get_channels

List currently available channels

POST

/join_channel

Join an audio channel

POST

/follow

Follow another user

GET

/get_events

Retrieve the Upcoming for You event feed

POST

/start_phone_number_auth

Start phone number authentication

POST

/complete_phone_number_auth

Complete phone number authentication

POST

/me

Get the current user

POST

/get_profile

Look up a user profile by ID

GET

/get_channels

List currently available channels

Why though Jentic?

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

Credential isolation

The Clubhouse access token (obtained via the phone number auth flow) is stored encrypted in the Jentic vault (MAXsystem) and applied as the Authorization header only at execution time. The agent never sees the raw token, and it is not written into prompt history.

Intent-based discovery

Agents search by intent (e.g. 'list upcoming clubhouse events' or 'follow a user') and Jentic returns the matching Clubhouse operation with its input schema, so the agent can call /get_events or /follow without reading the reverse-engineered docs.

Time to first call

Direct integration: 1-2 days to handle the phone auth flow, token refresh, and brittle endpoint shape. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Discord API

Discord offers persistent voice and text channels with an official API and bot framework

Choose Discord for an officially supported voice/community surface; this Clubhouse API is unofficial and brittle by comparison

Alternative

Twitter API

Twitter (X) Spaces is a comparable social audio feature available via the official Twitter API

Choose Twitter Spaces via the Twitter API for a supported social-audio integration; this Clubhouse spec is not vendor-maintained

Complementary

Slack API

Slack provides team chat where Clubhouse event summaries and follow notifications can be posted

Use Slack to post a daily digest of Clubhouse rooms a user follows, fetched from /get_events

FAQs

Specific to using Clubhouse API API through Jentic.

What authentication does the Clubhouse API use?

The Clubhouse API uses phone-number-based sign-in. Call /start_phone_number_auth with a phone number, /complete_phone_number_auth with the SMS verification code, then send the returned access token on subsequent requests. The OpenAPI specification does not declare a security scheme component, so the bearer token is set on the Authorization header by the client.

Is the Clubhouse API official?

No. This specification is reverse-engineered from public app traffic and is not maintained by Alpha Exploration Co. Endpoints, parameters, and behaviour can change without notice. Use only against accounts you own and respect the Clubhouse terms of service.

Can I list and join Clubhouse channels with this API?

Yes. GET /get_channels returns currently available channels, /join_channel takes a channel ID and joins the audio room, and /leave_channel exits it. The channel listing is the same one the app uses on its hallway view.

How do I look up a Clubhouse user profile?

Call POST /get_profile with the target user_id to retrieve the profile, including bio, follower counts, and joined clubs. /get_following returns who that user is following, and /me returns the current authenticated user's profile.

What are the rate limits for the Clubhouse API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. Because this is an unofficial spec, expect mobile-app-typical throttling and avoid bursts. Integrations should back off aggressively if requests start failing.

How do I retrieve upcoming Clubhouse events through Jentic?

Install the SDK with pip install jentic, search for 'list upcoming clubhouse events', load the clubhouseapi.com /get_events operation, and execute it. Jentic supplies the access token from the vault and returns the structured event feed.