Skip to main content
Pusher requires an authorization token before a client can subscribe to a private channel. When subscribing, the Pusher client sends socket_id and channel_name to your authorization endpoint. API bots call Futuur’s channel authorization endpoint:
POST https://api.futuur.com/v2.0/pusher/user-auth/ is also available and unchanged. Authenticate with HMAC headers (Key, Timestamp, HMAC). The string to sign is every parameter — Key, Timestamp, channel_name, and socket_id — sorted by name in case-sensitive code-point order, so the capitalized Key and Timestamp come first:
Do not sort with localeCompare. It is case-insensitive and puts channel_name before Key, which gives a signature the server rejects with 401 authentication_failed. Encode the values the way Python urlencode does. See Authentication for the exact rules.
On the phase-one preview host, use the base URL from Environment.
A user may only subscribe to their own private-user-{user_id} channel; any other private or presence channel returns 403. Your user ID is the id in GET /me/. Public channels (event and event-{event_id}) do not require authorization. The endpoint returns {"auth": "..."} on success. Its errors are plain {"detail": "..."} bodies: 400 when channel_name or socket_id is missing, 401 when the HMAC check fails, 403 for a channel that is not yours.