Real, copy-and-run configuration for the OddSockets packages that actually exist, generated from the endpoint this page is connected to right now.
| Status | connecting… |
|---|
| Manager URL | – |
|---|---|
| API key | – |
| Demo channel | – |
This is the shared public playground key, rate limited and open to anyone reading this page. Swap it for your own key from the dashboard before shipping anything.
The same package this page is running. Load it from a CDN or install it from npm.
There is no separate React package. React uses the JavaScript SDK directly; here is a hook that owns the connection lifecycle.
Server-side publishing from an ordinary Express route. No middleware package is required; the SDK is the integration.
Same API surface as the browser SDK, packaged for React Native's transport stack.
OddSockets is a hosted service, so integrating it into a deployment target means passing two values to your own application. There is no OddSockets container or deploy action to install.
A backend with no socket library can still publish. The button below sends this exact request from your browser and prints the real response. If the live connection at the top of the page is up, the message should also arrive over the socket — the panel says whether it did.
The manager serves its own OpenAPI document. The collection below is generated from the endpoints this page actually uses, not from a stored file.