REST
Hosted mock endpoints
Serve public JSON or text responses with status codes, headers, delays, and path params.
Mock API Platform / REST + WebSocket
SignalDock gives frontend developers, QA teams, and demo environments a browser-first way to publish mock REST endpoints and Socket.IO events under one clean workspace URL.
REST
Serve public JSON or text responses with status codes, headers, delays, and path params.
Realtime
Trigger namespaced events from the dashboard and keep frontend state machines moving.
Guardrails
Track hits, monitor triggers, and automatically block noisy IPs when traffic spikes.
Single entry auth
If the username already exists, SignalDock signs you in. If it does not, SignalDock creates the workspace with a hashed password and starts the session immediately.
What you get
Mock API Builder
Define methods, paths, status codes, headers, delays, and templated responses without opening Postman collections or spinning up a local mock server.
WebSocket Mocking
Create Socket.IO namespaces, author payload templates, and manually trigger event broadcasts for notifications, chats, feeds, and order lifecycles.
Operational Guardrails
SignalDock tracks usage, exposes last-hit activity, and automatically enforces per-IP rate limits with temporary blocks so public mocks stay usable.
How it works
Instead of juggling a local mock server, generated JSON files, and separate event tooling, SignalDock keeps the full contract-testing flow in one dashboard.
01
Add a route or event, then paste a payload template with placeholders.
02
Use the public workspace URL in frontend apps, QA suites, or product demos.
03
Inspect hit counts, last activity, and block status directly in the dashboard.
FAQ
The homepage is optimized to explain what the product does, while the app itself stays focused on fast creation, testing, and event triggering.
Frontend developers, QA engineers, mobile teams, demo environments, and integration testers who need hosted mock APIs or mock WebSocket events without backend dependencies.
Yes. Response and payload templates support tokens like `[[UUID]]`, `[[NAME]]`, `[[EMAIL]]`, `[[NUMBER_100000_999999]]`, `[[NOW_ISO]]`, and `[[USERNAME]]`.
That is one of the main use cases. The app exposes public workspace URLs and includes rate limits plus temporary IP blocking to reduce abuse during shared demos.