Fast integration
Use the standard browser WebSocket API. No framework lock-in, no custom client runtime required.
Secure WSS endpoint
wss://wssapi.keybit.co.uk
Credential-based auth
Public key plus secret credential
Built for integration
Plain text and JSON messages
Developer quick start
Connect, authenticate, then send messages.
Generate keys in your account, connect to the WSS endpoint, send an auth payload, then publish messages when the socket reports authentication success.
- Create or log in to your account.
- Add a labelled API key in Manage Keys.
- Reveal the secret credential and store it securely.
- Authenticate each WebSocket client before sending app messages.
const socket = new WebSocket('wss://wssapi.keybit.co.uk');
socket.onopen = () => {
socket.send(JSON.stringify({
action: 'auth',
publicKey: 'YOUR_PUBLIC_KEY',
privateKey: 'YOUR_SECRET_CREDENTIAL'
}));
};
socket.onmessage = (event) => {
const data = JSON.parse(event.data);
if (data.status === 'ok') {
socket.send(JSON.stringify({
type: 'update',
message: 'Hello from Socket API'
}));
}
};Why teams use it
Simple real-time messaging with the operational details handled.
Credential control
Create labelled keys, copy public keys, reveal secrets only after password confirmation, and remove keys when they are no longer needed.
Flexible payloads
Send plain text or JSON payloads for dashboards, live operations views, notification panels, and collaborative tools.
UK-focused hosting
Designed for UK projects that want predictable, low-friction real-time transport and clear GBP commercial discussions.
Use cases
Use Socket API anywhere your UI should update instantly.
Live dashboardsPush status, metrics, and operational changes without polling.
NotificationsDeliver alerts to connected web clients as events happen.
Chat and collaborationBroadcast messages and shared state between active users.
Queues and workflowsKeep interfaces in sync as jobs, orders, or tasks move state.
Account flow
Everything starts with a labelled API key.
Create a key per project or environment so credentials stay easy to identify and remove later.
Plans
Start in sandbox, scale when your usage is clear.
Sandbox
For testing, prototypes, and low-volume validation.
Project
For production apps with predictable message volume and standard support requirements.
Enterprise
For higher usage, integration support, SLAs, and custom operational requirements.
FAQ
Common questions
Which endpoint should my app connect to?
Use wss://wssapi.keybit.co.uk for WebSocket connections.
Should I expose my secret credential in browser code?
Only expose credentials in controlled test scenarios. For production, keep secret credentials server-side or behind your own trusted access layer.
Can I send JSON messages?
Yes. Socket API supports JSON strings and plain text messages over a standard WebSocket connection.