Skip to content

Endpoints

Endpoints are unique URLs that capture incoming webhooks. Each endpoint has its own request history, mock response configuration, and settings.

Updated Nov 2026

Creating an endpoint

Click New Endpoint in the dashboard. Give it a name and configure an optional mock response.

Each endpoint gets an auto-generated slug that forms its webhook URL:

https://go.webhooks.cc/w/<slug>

Endpoints on an account also receive email at <slug>@mailhooks.cc (Email Capture). Copy the URL and the address from the bar above the request list. Endpoints created by logged-in users, on any plan, never expire: they persist until you delete them manually or programmatically. Only ephemeral endpoints (created without an account or explicitly marked ephemeral) auto-delete after 12 hours.

Switching endpoints

Use the endpoint switcher dropdown in the dashboard header to switch between endpoints. The request list updates in real-time when you switch.

Favourite endpoints

Click the star next to the endpoint switcher to mark the open endpoint as a favourite. Favourites are listed first in the switcher, and the dashboard opens your first favourite when you go to it without picking an endpoint. Click the star again to remove it.

Favourites are yours alone: on an endpoint shared with your team, each member keeps their own. They follow your account to every browser and to both webhooks.cc and mailhooks.cc, and the API, the SDKs, the CLI and the MCP server see them too.

Sending test webhooks from the dashboard

Use the Send button in the endpoint bar to send a manual request or a signed provider template. 34 templates are available, including Stripe, GitHub, Shopify, Twilio, Square, HubSpot, Sentry, DocuSign, Adyen, PayPal, Plaid, Resend, and WorkOS.

See Dashboard test webhook docs for template presets, signature headers, and verification tips.

Endpoint settings

Open the Settings tab under the endpoint name. You can:

  • Rename the endpoint, choose which site lists it (webhooks.cc, mailhooks.cc or both), and name email fields
  • Read emails with layouts
  • Configure a mock response and response rules
  • Forward what it captures to up to 10 destinations (your servers, Slack or Discord, Google Sheets, file drops), or notify a channel when a request arrives
  • Share it with your teams
  • Configure signature verification: select a provider and paste your signing secret to automatically verify every incoming webhook
  • Keep requests for fewer days than your plan, or only until they are delivered (see Retention)
  • Get alerts when email fields stop matching, mail stops arriving or deliveries fail
  • Delete the endpoint and all its captured requests

Retention

Settings, Retention says how long the endpoint keeps what it captures:

  • Your plan's days (the default).
  • Fewer days: any number of days up to the plan's. Requests older than that are deleted within the hour, with their stored emails and attachments.
  • Deliver, then delete: each request is deleted a minute after every destination has its copy or has given up, for mail you must not keep. The dashboard still shows requests as they arrive; an endpoint without destinations keeps nothing past that minute.

Through the API, PATCH /api/endpoints/{slug} with retentionDays (a number, or null for the plan's) and deleteAfterDelivery. Only the endpoint's owner can change it.

Limits

PlanEndpointsRequestsRetention
FreeUnlimited50 per 24-hour window7 days
ProUnlimited100,000 per month31 days
BusinessUnlimited250,000 per month90 days

See Plans & Limits for full details on quotas, retention, rate limits, and billing periods.