The Pusher-compatible API
WordPlus Cloud also speaks the Pusher Channels protocol, version 7, for plugins and code already built for it. The Pusher client and server libraries, and the plugins built on them, work with it as they are: point them at the hosts below and give them your site keys.
For new code, use the realtime SDK instead: for WordPress, or for other websites and apps. It shares one connection per page with the WordPlus plugins, seals what it carries with keys only your site holds, and comes with calls, group calls and the site users built in.
WordPlus plugins do not use this API: they talk to the cloud over their own protocols, made for what they do, and need no keys from here. A plugin built for Pusher opens its own connection beside theirs.
Your keys
Each site on your WordPlus Cloud subscription has its own app ID, key and secret, in your account under Sites → Realtime API keys. A site without any of our plugins gets them too: add it under Sites → Add site.
Settings
| Setting | Value |
|---|---|
| WebSocket host | ws.wordplus.cloud |
| HTTP API host | rest.wordplus.cloud |
| Port | 443, TLS on |
| App ID, key and secret | those of your site, from Sites → Realtime API keys. Keep the secret on your server, never in a page. |
| Cluster | any value, such as mt1, for a library that asks for one: the host above is the one used |
The browser connects to the WebSocket host. Your server sends events through the HTTP API host. Examples show both with the Pusher libraries.