Can my team share one webhook URL and see the same requests?

Yes. Share an endpoint with your team and every member sees its requests live in the dashboard, with headers, body, query and signature checks. Members can also stream it from the CLI, SDK or MCP server and forward it to their own localhost.

How much does webhooks.cc cost for a team?

$12 per seat per month, billed per team on a 30-day period. Each seat is one member, the owner included, and adds 100,000 requests per 30 days to a pool the whole team shares. A team of 5 pays $60 a month for 500,000 requests.

Do team members need a paid plan?

No. Members can be on the Free plan. Requests on endpoints shared with an active team draw from the team's pool and keep 31-day retention, whatever plan the endpoint owner is on.

Which webhook testing tools support longer retention and access control for teams?

On webhooks.cc, team-billed requests are kept for 31 days and shared endpoints can only be read by signed-in team members. Guest URLs on any tool, webhooks.cc's included, are readable by anyone who knows the address, so a team should capture on shared account endpoints instead.

What happens when the team's quota runs out?

The receiver answers 429 Too Many Requests with a Retry-After header pointing at the team's period reset, so well-behaved senders retry later. Add seats to raise the pool at once; the added seats are charged their share of the current period.

Is there a free trial for Teams?

Every webhooks.cc feature works on the free personal plan, so you can try capture, replay, the CLI and the SDK on your own first. A team itself starts working once it has an active subscription; until then it is kept but suspended.

Can we cancel or change the number of seats?

Yes. Added seats are charged right away for the rest of the period. Removed seats stay until the renewal, which then bills the lower count. Canceling keeps the team active until the period ends; nothing is deleted.

Webhook testing for teams

Share webhook endpoints with your team. Everyone sees the same requests the moment they arrive, replays them against their own code, and stops pasting payloads into chat. $12 per seat per month, with every seat adding 100,000 requests to one shared pool.

Any account can create a team. Read the Teams docs for every detail.

What teams use it for

One staging endpoint for everyone

Point Stripe test mode, GitHub or Shopify at one shared URL. Every developer sees each delivery as it arrives, instead of one person's ngrok tunnel catching it.

QA sees what their click triggered

A tester places an order and finds the webhook it fired in the shared list, with headers, body and signature check, without asking a developer to dig through logs.

Debug a delivery together

Capture the payload that broke production on a shared endpoint, link it in the incident channel, and replay it against a fix on anyone's machine.

Each developer forwards to their own localhost

whk tunnel 3000 --endpoint <shared-slug> streams the team's endpoint to a local handler. Several people can listen to the same endpoint at once.

Feature checklist

Shared endpoints visible to team members only, after sign-in
31-day retention for every team-billed request, on any personal plan
Live updates in the dashboard and over SSE for every member
Replay any captured request to any URL
Search across path, body and headers
Mock responses members can edit; signing and forwarding stay with the endpoint owner
Email capture: each shared endpoint has its own address
CLI, TypeScript SDK and MCP server see shared endpoints like your own
Owner-only delete, sharing, invites and billing
Pooled quota: 100,000 requests per seat per 30 days

Set up a team in four steps

1
Create a team
Open Teams from the avatar menu and pick a name. Any account can create one, Free or Pro; you become the owner.
2
Choose seats and subscribe
Each seat is one member, the owner included, and adds 100,000 requests per 30 days to the team's pool. $12 per seat per month.
3
Invite your team
Invite anyone by email. People without an account find the invite waiting after they sign up with that address.
4
Share endpoints
In an endpoint's Settings tab, share it with the team. Members see it under Shared with me, and its requests bill to the team.

Who can do what

Action	Owner	Member
View requests	Yes	Yes
Edit mock response	Yes	Yes
Rename endpoint	Yes	Yes
Delete endpoint	Yes	No
Share or unshare endpoints	Yes	No
Invite and remove members	Yes	No
Manage billing	Yes	No

Shared endpoints are only readable by signed-in members. Members cannot delete an endpoint or clear its requests, and its signing, forwarding, email and notification settings stay with the person who owns it.

Pricing

Billed per team, not per account, on a 30-day period that starts when the team subscribes. Prices include VAT where it applies.

3 seats

$36/mo

300,000 requests per 30 days

5 seats

$60/mo

500,000 requests per 30 days

10 seats

$120/mo

1,000,000 requests per 30 days

Team plans compared

webhooks.cc	$12/seat/mo, pooled quota
Webhook.site	Enterprise only, from $69/mo
Beeceptor	Team+ ($25/mo), unlimited members
Hookdeck	Team+ ($39/mo), unlimited seats
ngrok	$20/mo incl. 3 seats, then $5/seat
Smee.io	None (anonymous channels)

Other tools' prices as listed on their sites when we compared; check them before you buy. All comparisons

Shared endpoints from the CLI

An API key carries the team access of its account, so shared endpoints work like your own in the CLI, the SDK and the MCP server.

whk list --team Payments
whk listen <shared-slug>
whk tunnel 3000 --endpoint <shared-slug>
whk teams share my-stripe --team Payments

Teams questions

Bring your team in

Create a team, pick your seats, and share your first endpoint.

How Teams works