Teams

Built for agencies with more than one client

Share endpoints, everything they receive, and the store credentials behind them. No more forwarding payloads in Slack.

👥One endpoint, everyone sees it

A team endpoint appears for every member with its full history: payloads, headers, search, and replay. Whoever is on shift can debug the client's webhook without waiting for the person who set it up.

🔐Connect a store once

An admin saves the client's store credentials, encrypted: a BigCommerce token, a WooCommerce key pair, a Square access token, a Shopify custom app token or a Stripe API key. The whole team can then register webhooks against that store. Members can use the credentials and never read them, and only admins can remove them.

📝Know who did what

Shared endpoints record who created them, so a busy account stays readable months later.

🤖The API and MCP come too

Team endpoints appear through the REST API and the MCP server with the same key you already use, so an agent can read a colleague's captured payload without anyone copying JSON around.

💷Cheaper as you grow

Pay per seat, from 2 seats up. Later seats cost less, and adding someone never raises the price of the seats you already have.

Bands work like tax brackets: the first seats always cost the same, and only the seats above a threshold get the lower rate.