Socket Chief
Socket Chief uses the Pusher WebSocket protocol and the Pusher HTTP API, so you integrate with existing Pusher client and server libraries. It does not have a separate Chief Tools API yet. Manage applications, channel types, and webhooks from the Socket Chief dashboard for now.
Looking for help using Socket Chief in the browser? Go to the Socket Chief documentation.
Connect a Pusher library
Copy the connection settings from your application page in Socket Chief, then use them in place of Pusher's:
- Use the App ID / App Key value as both the app ID and the app key.
- Use the App Secret only on your server. It signs HTTP API requests, private and presence channel authorizations, and webhooks.
- Use the Host as
wsHostin client libraries and as the host in server libraries, with the Port shown. - Always connect over TLS, with
forceTLSin clients andhttpsin server libraries. - Set any cluster value, such as
eu, if your library requires one. Socket Chief ignores it.
For channel authorization, events, webhooks, and HTTP API requests, follow the Pusher Channels documentation and the docs for your library.
Request API access
If your integration needs to manage Socket Chief applications through an API, tell us what it should do. Suggest it on the roadmap or contact us. Real use cases decide what the API covers first.