Let Your Customers Debug Their Own Webhooks
If your product sends webhooks out to its customers, every "my webhook isn't firing" and "can you resend that event?" becomes a support ticket that ends up on an engineer's desk. Hookbase ships an embeddable React component library that puts endpoints, subscriptions, delivery logs, and replay directly in your own UI — so the customer answers the question themselves.
A Portal That Lives Inside Your Product
The portal isn't a Hookbase-branded page you send customers off to. It's the @hookbase/portal React package that you render inside your own app, authenticated with a scoped portal token instead of your main Hookbase API credentials.
Embeddable Components
Import the pieces you want — endpoint list and form, subscription manager, message log — and lay them out however your settings page is already organized.
Scoped Portal Tokens
Each session is authenticated with a portal token carrying read or write scope, tied to a single application. A customer only ever sees their own data — never yours, and never another customer's.
Themeable
Pass a theme with your own colors and border radius, and set dark mode to light, dark, or auto, so the portal reads as part of your product rather than a bolted-on iframe.
Rendering the portal in your settings page
import {
HookbasePortal,
EndpointList,
EndpointForm,
MessageLog,
} from '@hookbase/portal';
import '@hookbase/portal/styles.css';
<HookbasePortal token={portalToken}>
<EndpointList />
<EndpointForm />
<MessageLog />
</HookbasePortal>Your backend mints the portal token for the signed-in customer; the components handle fetching, loading states, and errors from there.
Everything They'd Otherwise Email You About
Each of these is a support ticket today. In the portal, it's something the customer does themselves, scoped to their own application.
Endpoint Management
Customers create, update, and delete their own webhook endpoints from inside your app — pointing at whatever URL they want, and disabling one without deleting it while they redeploy.
Secret Rotation
A customer can rotate their endpoint's signing secret themselves. No support thread, no engineer pasting a new secret into a ticket, no secret sitting in someone's inbox.
Subscription Management
Customers pick which of your event types they actually want. They subscribe and unsubscribe on their own, so you stop sending events nobody consumes and stop fielding requests to add one.
Delivery History & Attempt Logs
Every message sent to their endpoint, with the per-attempt log behind it. When a customer says a webhook never arrived, they can check the response their own server returned before they ask you.
Test Delivery
Send a test delivery to an endpoint straight from the portal to confirm the URL, firewall rules, and signature verification are wired up correctly — during onboarding, not after the first real event fails.
Replay a Failed Delivery
If one of their deliveries failed, the customer can replay it once their endpoint is healthy again — turning "can you resend that event?" into a button they press themselves.
The portal exposes a scoped slice of the same machinery behind webhook destinations and webhook replay. Same delivery logs, same replay path — just narrowed to one customer's own traffic.
Why This Matters
Outbound webhooks generate a support load that scales with your customer count, and almost none of it needs a human.
Without a customer portal
With the Hookbase portal
The onboarding case matters just as much as the debugging one: a customer who can add an endpoint and fire a test delivery on their own gets to their first successful webhook without waiting on anybody.
Stop Answering Webhook Tickets
Install @hookbase/portal, mint a portal token for the signed-in customer, and ship a self-serve webhook page in your product. Get started free — no credit card required.
Start Free