Skip to main content
The words that come up most, defined. Each links to a deeper explanation where there is one.
Your workspace — the tenant that owns everything: endpoints, events, team members, and billing. You can belong to more than one. “Team” refers to the people in an organization, not a separate thing.
A single ingest URL and its settings. You point a provider at an endpoint’s URL, and every request to it becomes an event. An endpoint can be paused, resumed, and configured for verification and deduplication.
The permanent web address that receives requests, on the dedicated wbhk.my domain (https://wbhk.my/…). It’s signed and re-viewable, and unknown addresses return a 404.
One captured request. The raw bytes are written down the moment a request arrives, so you always have a durable copy to inspect, replay, and deliver. See events and usage.
Checking that a request genuinely came from the provider it claims to. Register the provider’s signing secret and each event gets a verification state: verified, authenticated, failed, or unattempted.
The service sending you webhooks — Stripe, GitHub, Shopify, and 139 others. Each has a known way of signing its requests that webhook.co checks for you.
A service you forward events to. Destinations are an HTTPS allowlist; webhook.co delivers events to them with retries and dead-lettering.
One attempt to send an event to a destination. Deliveries retry on failure and are dead-lettered once the schedule is exhausted.
Re-sending an event you’ve already captured — to your laptop with wbhk listen, or to a destination — instead of asking the provider to send it again. See replay to localhost.
Optionally collapsing repeated requests that mean the same thing, so a provider retrying doesn’t create duplicate events. Configured per endpoint — see deduplication.
A whk_ secret that authenticates the API, CLI, and scripts to your organization. Managed under Credentials — see authentication.