Mock WebSocket server
Test live clients with echo, scripted messages, close codes and an inspectable traffic log.
Connect your client
Create a mock to get a WebSocket URL and see its connection, message and close events here.
About Mock WebSocket server
Host an expiring WebSocket endpoint to test live messages, reconnects and connection failures.
When to use it
Host an expiring WebSocket endpoint to test live messages, reconnects and connection failures.
{"name":"Live updates","routes":[],"websocket":{"echo":true,"welcome":["ready"],"replies":[{"match":"ping","reply":"pong"}]}}How to use it
- Configure the endpoint and choose private or public access.
- Create it and send requests from your client.
- Inspect test output, update or delete the resource when finished.
Limits & privacy
Uses an expiring mock resource, private by default, with separate management and access credentials. Public access is optional. Standard resource quotas, ownership, renewal and deletion apply. Private access tokens are sent in headers, never in share URLs. Echo text or binary, send welcome messages in order, match exact text and set a reply delay or close code. Connections last up to one minute and accept messages up to 16 KiB. Inspect traffic with inspect_mock_api or the mock calls API. Private clients can use X-Access-Token in the handshake. Use synthetic messages because traffic previews are retained.
Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.