Clubhouse API
★ Only Publicly Available OpenAPI DocumentSocial 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.
Use for: Start a phone number authentication flow for a Clubhouse account, Complete the phone authentication using the verification code, Look up a Clubhouse user profile by ID, List the channels currently active on Clubhouse
Not supported: Does not handle live audio streaming, content moderation, or ad delivery - use for Clubhouse profile, club, channel, and event metadata operations only.
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.
Install Jentic One Beta
Connect the Clubhouse API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clubhouse 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclubhouseapi.com%2Fclubhouseapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclubhouseapi.com%2Fclubhouseapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Clubhouse 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
Retrieve the Upcoming for You event feed and per-topic clubs and users
Use Cases
Patterns agents use Clubhouse 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
POST
/join_channel
Join an audio channel
POST
/follow
Follow another user
GET
/get_events
Retrieve the Upcoming for You event feed
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring this Clubhouse API by hand means running its phone-number auth flow to obtain a token, targeting www.clubhouseapi.com, and handling retries across reverse-engineered endpoints yourself. Through Jentic you install once, import the Clubhouse API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Clubhouse works over profile, club, channel, and event endpoints, so scope the agent to the operations it needs, such as getting channels or listing events. You choose that set, so operations like joining a channel or following a user are not included unless you add them.
Credential isolation
Your Clubhouse access token is stored once, encrypted, by your own Jentic One instance and applied as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list upcoming Clubhouse events' or 'follow a user', and Jentic returns the matching Clubhouse operation with its input schema so the agent calls the right endpoint without reading the reverse-engineered docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Clubhouse 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.
Can I limit what my agent is allowed to do with the Clubhouse API?
Yes. Because Jentic One is self-hosted, you decide which Clubhouse operations your agent may call, and your own rules govern the stored access token it uses. You can scope it to read-only endpoints like GET /get_channels, /get_events, and /get_profile while excluding state-changing operations such as /join_channel, /follow, or /update_notifications. Only the operations you add to the agent's set are available to it, so nothing runs against your account unless you have explicitly allowed it.
GET STARTED