How the platform works

Core ideas

You choose a unique endpoint id (for example stripe-orders-prod). The capture URL POST /api/webhook/{id} accepts requests from any provider; the app records the payload so you can debug without standing up a server.

The Inspector at /webhook/{id} is the live view of that stream: body, headers, query, and raw views, plus filters and pause when you need a quiet moment.

Pipe Studio attaches one or more pipelines to the same endpoint. A pipeline is a versioned handler: you publish immutable bundles; production webhooks run the enabled pipeline’s current live version.

Typical journey

• Create or register the endpoint from the home page or your account.
• Send a test POST to the capture URL and open the Inspector to verify shape and headers.
• Open Pipe Studio for that endpoint, configure the event and graph, write handler code, run tests, then publish.
• Automate publishes from CI with the CLI or call the pipelines API directly when you need full control.

Auth and tiers

You can start in guest mode; signing in lets you claim endpoints and unlock tier features (private endpoints, share links, pipeline limits, execution time).

Programmatic access uses the same rules as the dashboard: browser session or an API key from Account (Authorization: Bearer or X-Api-Key). See Pricing for limits that apply to pipelines, bundle size, and HTTP steps.