My webhook isn't showing up in Eventfy — what should I check?

Confirm the exact catch URL was pasted into the provider with no trailing characters missing, check the provider's own delivery log for the HTTP status Eventfy returned (it should be 200), and confirm the workspace shown in the dashboard is the one the URL belongs to.

Why is my local server not receiving forwarded events from the CLI?

Check that eventfy listen is pointed at the correct port and lens token, that your local server is actually running on that port, and that no firewall or VPN is blocking outbound connections from the CLI process.

How do I cancel my Eventfy subscription?

From the dashboard, go to Settings then Billing, and use the Cancel button. You keep access until the end of your current billing period.

Help & Support

Troubleshooting for the things that actually go wrong, and how to reach a human if this page doesn't cover it.

Receiving events

Webhooks not showing up, delivery failures

Local forwarding

CLI connection and eventfy listen issues

Account & billing

Plans, cancellation, payment questions

Security

Signature verification, API key safety

All systems currently operational — this section is generated at build time, not live. For real-time status, contact us below.

Receiving events

My webhook isn't showing up in Eventfy at all

Check the provider's own delivery log first — most platforms (Stripe, GitHub, Shopify) show you the HTTP status their webhook attempt received. If it shows a non-200 response or a connection failure, the URL pasted into the provider may have a typo or a missing/extra character. Copy it fresh from the dashboard rather than retyping it.

Events are arriving but under the wrong workspace

Each catch URL belongs to exactly one workspace at creation time — check which workspace the dashboard is currently showing (top left) and switch if needed. The URL itself doesn't change when you switch workspaces; only which workspace's events you're viewing does.

The event arrived but the payload looks truncated or malformed

Eventfy stores exactly what was received on the request body — if it looks malformed, the sender likely sent it that way. Check the raw payload in the inspector against what the provider's own docs say they send for that event type.

Local forwarding (CLI)

eventfy listen connects but my local server never receives anything

Confirm the port passed to listen matches the port your local server is actually bound to, and that the server is running before you start forwarding. A firewall or VPN blocking outbound connections from the CLI process is the next most common cause.

The CLI shows "unauthorized" when running a test suite

Test suites run via CI or terminal need an API key passed with --key — a browser session doesn't apply here. Grab the key from the dashboard's Advanced panel on any webhook URL in that workspace.

Account & billing

How do I cancel my subscription?

Settings → Billing → Cancel. You keep access until the end of your current billing period; nothing is deleted immediately.

Can I switch plans?

Yes, from Settings → Billing. Moving to a plan with lower webhook-URL or workspace limits than you're currently using will be blocked until you're back under the new limits. Downgrading from Enterprise also turns off Slack/Discord alerts.

I forgot my password

Password resets aren't self-service yet — contact us below and we'll help you regain access.

Security

How do I verify a webhook actually came from the provider, not someone spoofing it?

Eventfy passes through the original signature header (e.g. Stripe's Stripe-Signature) unmodified — verification happens in your own handler code exactly as the provider's docs describe, the same as if the webhook had gone directly to you.

Someone else has my API key — what do I do?

There's currently no self-service key rotation — contact us and we'll issue a new key for the workspace and invalidate the old one.

Still stuck? We read every message.

Email [email protected]