Pusher Docs Reference

Our Quick Start covers JavaScript. Use pusher-js with wsHost: "ws.soketify.com".

Install pusher-websocket-swift via SPM. Replace the cluster with wsHost: "ws.soketify.com" and set useTLS: true.

Install pusher-websocket-android via Gradle. Replace cluster with the Soketify WebSocket host.

Use pusher_channels_flutter. Pass host: "ws.soketify.com" and cluster: "default".

Same as the JavaScript quick start; pusher-js works in React Native. Point wsHost to ws.soketify.com.

Fully compatible: swap the Pusher app credentials for your Soketify credentials and update wsHost.

Uses presence channels, fully supported. See our Channels and Authentication docs.

Covers pusher-js API: bind, unbind, subscribe, unsubscribe. All methods work identically.

Fully covered: states, socket_id, error codes, disconnection.

Connection-level user auth (pusher.signin(), pusher.user). Supported by Soketi. Requires a /pusher/user-auth endpoint returning a signed token. Not the same as channel authorization.

Notifies you when specific users go online/offline across any connection. Requires user authentication (pusher.signin). Supported by Soketi; enable via app settings and provide a watchlist in your user-auth endpoint.

Pusher Functions is a serverless compute feature specific to Pusher's cloud. Not available in Soketify. Use a regular serverless function (Cloudflare Workers, Vercel, etc.) and trigger events via the REST API instead.

Connection-level authorization that locks a connection to a specific user. Implemented alongside user authentication. Supported by Soketi.

All five channel types (public, private, encrypted, presence, cache) are documented here.

Binding, unbinding, system events, client events, naming rules: all covered.

Covers pusher-js init options: activityTimeout, pongTimeout, enabledTransports, disabledTransports, authEndpoint, auth headers, etc. All options work. Key difference: set wsHost / wsPort / wssPort instead of cluster.

pusher-js can fall back to SockJS (xhr_streaming, xhr_polling) on networks that block WebSockets. In our Quick Start we set enabledTransports: ["ws", "wss"] which disables fallbacks for simplicity. Remove that option to enable them. Required for: corporate proxies, old mobile networks, HTTP-only environments.

See the Device Compatibility section on this page.

Trigger events, batch trigger, list channels, channel info, presence users.

Server endpoint for connection-level user auth (/pusher/user-auth). Complementary to our Authentication guide which covers channel authorization.

Server-side API to push events directly to a user_id rather than a channel name. Supported by Soketi. POST to /apps/{appId}/users/{userId}/events.

Force-disconnect all connections for a given user_id. POST to /apps/{appId}/users/{userId}/terminate_connections. Supported by Soketi.

Pass socket_id to trigger/triggerBatch to exclude the sender. Covered in the Events guide.

Every official Pusher server library works with Soketify. Pass host: "api.soketify.com" instead of using the cluster option.

Deep-dive into the HMAC-SHA256 signature scheme for both channel auth and REST API auth.

The low-level WebSocket protocol Soketify implements. Only relevant if you are building a custom client library.

What a conformant Pusher server library must implement. Useful if you are building an SDK.

Enable debug logging in pusher-js with Pusher.logToConsole = true. Works identically with Soketify.