What is a mock API webhook (and how to make one free)

A mock webhook is a real HTTPS endpoint that returns a response you define. Instead of standing up a server, you publish a payload to a URL and point your app, a third-party service, or a curl command at it. It's ideal for testing a client, receiving a callback, or stubbing an API that isn't built yet.

1. Sign in (a free account is enough to publish).
2. Put your response payload in the editor — JSON, XML, YAML, whatever your caller expects.
3. Open the Publish drawer in the toolbar and publish. You get a public URL back.

Anyone with the URL can call it — fetching the slug is public on purpose, so real services can send it traffic. The response's Content-Type matches the format you published.

A fixed payload returns the same bytes every time. To return a fresh UUID, the current timestamp, a random value, or an echo of the incoming request, wrap a small expression in {{ … }} — see Return dynamic data from a mock API.

Each webhook has a private inspection portal, visible only to you. It logs every incoming request — method, headers, query string, and body — so you can confirm what your client actually sent. From the portal you can also set a canned response status code and clear the log.

• Endpoints expire automatically after a set window (longer on paid plans) — mock URLs are meant to be temporary.
• Paid plans can publish to a custom, memorable path instead of a random slug.
• Decoding and inspection are owner-gated: only you can read the request log or change the response.

← All help articles · Dynamic mock API responses · Usage guide