socket.help

Streaming response simulator

Generate a controlled stream of response data.

Expires after 1 hour

Checking this session…

Import / export configuration
Request conditions & response templates

Templates accept {{path.id}}, {{query.name}} and {{body.name}} inside JSON strings or plain text. Missing values become empty strings. No code runs. Test credentials are stored in the configuration; use fake tokens only.

Up to 20 routes, 80 KiB total configuration, and 120 requests per minute. Paths support parameters such as /users/:id. Matching routes are checked in order.

Open an existing mock API

About Streaming response simulator

Create a text endpoint that sends each configured line at a chosen interval.

When to use it

Create a text endpoint that sends each configured line at a chosen interval.

Streaming response simulator example
first chunk → wait → second chunk

How to use it

  1. Configure the endpoint and choose private or public access.
  2. Create it and send requests from your client.
  3. 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. GET or ANY, status 200. Up to 20 lines of 4 KiB each, intervals of 10–1000 ms, and five seconds of delivery. Sixteen streams per server; proxy or client buffering can combine network chunks.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.