Clubhouse API

REST discovered

Details Spec supplied by APIs.guru

URL: https://www.clubhouseapi.com/api/
Spec: https://api.apis.guru/v2/specs/clubhouseapi.com/1/openapi.json
Spec (yaml): https://raw.githubusercontent.com/zhuowei/ClubhouseAPI/main/doc/openapi.yaml
Docs: https://documenter.getpostman.com/view/2651915/TzCQa6Wx

Authentication

Clubhouse auth token Authorization: Token <credential> + Clubhouse user ID header value CH-UserID: <credential> discovered

Clubhouse auth token bearer Get token ↗

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`.

Clubhouse user ID header value compound Get key ↗

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`.

Clubhouse access token (JWT) Authorization: Bearer <credential> + Clubhouse user ID header value CH-UserID: <credential> discovered

Clubhouse access token (JWT) jwt Get key ↗

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`.