When we launched Teams in March, it came bundled with Pro. That model had two problems. Every teammate needed their own Pro subscription just to accept an invite, and every webhook that hit a shared endpoint counted against one person's quota: the endpoint owner's. Sharing an endpoint meant volunteering your own request limit.
Today Teams becomes its own plan. A team carries its own subscription at $12 per seat per month, and every seat does two jobs: it holds one member, and it adds 100,000 requests per 30 days to a pool the whole team shares.
What changed
- Any account can create a team. The Pro gate is gone. A Free account can own a team, join a team, and share endpoints into it. Your personal plan and your team's plan are now separate things.
- The team pays for team traffic. Webhooks that hit a team-shared endpoint bill the team's pooled quota, not the endpoint owner's personal plan.
- Seats are the member cap. A team holds exactly as many members as it has seats, and the owner occupies one. Add a seat to add a member. Remove a member and the seat frees up for the next person.
The collaboration features are unchanged: shared endpoints update in real time for every member, stream in the CLI with whk listen, and work with the SDK. The March launch post covers those in detail, and the Teams docs stay current.
One seat, two jobs
A seat is both a member slot and 100,000 pooled requests per 30 days. The two scale together because they tend to grow together: more people on an integration usually means more webhook traffic worth inspecting.
| Seats | Price | Pooled requests per 30 days |
|---|---|---|
| 1 | $12/month | 100,000 |
| 3 | $36/month | 300,000 |
| 10 | $120/month | 1,000,000 |
The pool is shared, not per member. If one teammate's endpoint receives 250,000 requests this period and nobody else's receives any, a 3-seat team still has headroom.
Adjust seats any time from the team page; a team supports 1 to 1,000 seats. The one restriction: you can't reduce seats below the current member count. Remove members first, then reduce.
Billing is monthly and per team. Your personal subscription, if you have one, is unaffected.
How the pool gets billed
The exact rules:
- Once you share an endpoint with an active team, its webhooks bill the team pool. Your personal quota is untouched, on Free and Pro alike.
- An endpoint shared with several teams bills the oldest share. A request never bills two teams.
- Traffic on team-shared endpoints is retained for 31 days, whatever the endpoint owner's personal plan. A Free account's endpoint gets full retention while it's shared with an active team.
- When the pool runs out, the receiver returns
429 Too Many Requestswith aRetry-Afterheader pointing at the period reset. The pool refills every 30 days from the day the team subscribed.
Setting up a team
Create the team
Open Teams from your avatar menu and create a team. Any account works; you don't need Pro. You become the owner and occupy the first seat.
Pick a seat count and subscribe
Checkout defaults to 3 seats ($36/month). Pick what you need now; you can change it later from the team page.
Invite teammates
Invite by email. Teammates need a webhooks.cc account first (Free is fine). The invite appears on their Teams page, where they accept or decline. Accepting claims a seat.
Share endpoints
Open an endpoint's settings and share it with the team. From that moment its traffic bills the team pool, and every member sees requests arrive in real time.
Where Teams fits
| Plan | Requests | Period | Retention | Price |
|---|---|---|---|---|
| Free | 50 | 24 hours | 7 days | $0 |
| Pro | 100,000 | 30 days | 31 days | $8/month |
| Teams | 100,000 per seat, pooled | 30 days | 31 days | $12/seat/month |
Pro stays what it was: a personal plan for individual work. Teams covers the endpoints your whole group watches. Plenty of people will use both: Pro for personal test endpoints, a team for the shared staging integration.
If you cancel
Cancel any time from the team page. The team stays fully active until the end of the paid period, then suspends: invites, endpoint sharing, and member access pause. Nothing is deleted. Shared endpoints keep capturing; their traffic just bills the endpoint owner's personal plan again. Resubscribe and the team reactivates immediately, members and shares intact.
FAQ
Create your first team at webhooks.cc/teams.
Teams Documentation
Create teams, manage members and seats, and share endpoints.
Plans and Limits
Full breakdown of quotas, retention, and pricing across every plan.