socket.help

Mock response templates

Combine dynamic paths, conditions, and response templates.

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
Guide & examples

About Mock response templates

Build mock responses from named path segments, query parameters and top-level JSON body fields.

When to use it

Build mock responses from named path segments, query parameters and top-level JSON body fields.

Mock response templates example
GET /users/42?name=Ada → {"id":"42","name":"Ada"}

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. Placeholders are inserted into JSON strings or plain text. Missing fields become empty strings. No expressions, loops, scripts or remote calls.

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