Quickstart: dashboard

This path uses only the dashboard and works on the Free plan: no API key, no card. If you do not have a workspace yet, create an account; sign-up is a verified email, two-factor authentication (required on every account) and a workspace name. Prefer to script it? The API quickstart covers the same loop in three calls (API access starts on the Solo plan).

A Free workspace can hold 3 endpoints, keeps 100 stored requests per endpoint, and keeps them for 3 days. That is plenty for everything below.

1. Create an endpoint

Open Endpoints and choose New Endpoint. Give it a name you will recognise, such as quickstart (the name is optional), leave Provider on Generic endpoint, and choose Create. Open the new endpoint from the list if it has not opened for you.

2. Copy the capture URL

The strip at the top of the endpoint page is its capture URL, the address you give to webhook senders:

https://in.webhookvault.net/hook/01a06dca-5b36-738e-9e82-67af4d06bc31

Choose copy to put it on your clipboard. The curl button next to it copies a ready-made test command for this endpoint instead.

3. Send a test webhook

Any HTTP client works. Here is a stand-in for the provider you will wire up later. Replace the URL with your own capture URL:

curl -s -X POST "https://in.webhookvault.net/hook/<your-endpoint-id>" \
  -H "Content-Type: application/json" \
  -d '{"type":"order.created","order":{"id":"ord_123","total":4900}}'

A 200 back is the vault's word that the request is stored. The endpoint page updates by itself: open the Requests tab and the row is already there. It shows:

• the time it was received, with a POST chip;
• the event label order.created, read from the type field of the body;
• the size, 62 B;
• not checked under verification and not forwarded under forwarding, because you have not set up either yet.

4. Open the request

Select the row. The request opens with everything the vault stored:

• Payload: the body, pretty-printed and highlighted when it is JSON. copy puts the body on your clipboard and curl copies a command that re-sends this exact request (method, headers and body) to the capture URL.
• The line above the tabs: the method, the event label, the request id, when it was received, the size and the content type.
• Headers: every header the sender included, such as Content-Type and User-Agent.
• Query: the query string, one parameter per row.

Nothing is trimmed or reordered: this is the request as it arrived.

5. Optional: name the source provider

If the sender is a known provider, open the endpoint, switch to Configure, choose it under Source provider in General, and select Save. The explorer then labels each request with the provider's own event names (for example charge.refunded for Stripe) instead of guessing from the payload. The provider guides on the website show where to paste the capture URL in each provider's own settings. Everything else in this quickstart is the same for any sender.

Where next?

• Concepts: what a captured request and a delivery are, and every state a delivery can be in
• Forward and replay: relay captures to your own app and re-send any stored request
• Watchdogs: get alerted when an expected webhook stops arriving (Solo and up)
• Quickstart: API (Solo and up): the same loop from a script