clubhouseapi.com
Clubhouse was a social audio application centered on live voice rooms and clubs. The `clubhouseapi.com` domain served the app's backend API, which has been publicly documented through reverse-engineered community specs and collections.
clubhouseapi.com exposes one HTTP API at `https://www.clubhouseapi.com/api/`, documented by a public reverse-engineered OpenAPI spec and Postman collection, with authenticated calls using `CH-UserID` plus either `Authorization: Token <auth_token>` or `Authorization: Bearer <access_token>` obtained through phone-number auth.
- Clubhouse APIdiscovered
Authenticate by phone number against the Clubhouse API: call start_phone_number_auth to send an SMS (or call_phone_number_auth / resend_phone_number_auth), then submit the code to `complete_phone_number_auth`. The response includes auth_token and user_profile.user_id. The reverse-engineered API docs note authenticated requests use Authorization: Token <auth_token> together with CH-UserID: <user_id>. See the public Postman collection README and OpenAPI comments in `openapi.yaml`.
Authenticate by phone number against the Clubhouse API: call start_phone_number_auth to send an SMS (or call_phone_number_auth / resend_phone_number_auth), then submit the code to `complete_phone_number_auth`. The response includes access_token plus user_profile.user_id. The reverse-engineered OpenAPI comments say authenticated requests may alternatively use Authorization: Bearer <access_token> together with CH-UserID: <user_id>. See `openapi.yaml`.
Complete the phone-number authentication flow at `complete_phone_number_auth`. Read user_profile.user_id from the response and send it as the CH-UserID header on authenticated requests, alongside either auth_token or access_token. The required header pairing is documented in comments in `openapi.yaml`.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing