Yes, Web Hook Box offers a free tier with basic functionality. We also offer premium features for donors who support the project. Check the pricing page for more details on the differences between free and donor tiers.

Yes, an account is required to use Web Hook Box. This allows us to provide you with a dedicated dashboard to manage your webhooks, view history, and configure forwarding rules. We use Firebase authentication for secure and easy login.

To set up forwarding, go to your webhook details page and click on "Configure" in the forwarding section. Enter the destination URL where you want the webhooks to be forwarded and select any additional options like header forwarding or custom responses.

Yes, with the webhook transformation feature (available to donors), you can modify the headers, query parameters, and payload before forwarding. This is useful for testing different scenarios or adapting the webhook format to match your endpoint's requirements.

If your endpoint is unavailable when a webhook is forwarded, Web Hook Box will record the failure and display it in your dashboard. With our retry feature (available to donors), you can configure automatic retries with customizable backoff settings to ensure delivery once your endpoint is back online.

For free accounts, webhook data is stored for 7 days. Donor accounts can access webhook history for up to a month. You can manually delete webhook data at any time from your dashboard. For more details, please refer to our Security documentation.

Yes, all webhook data is encrypted in transit using HTTPS. Additionally, sensitive data stored in our database is encrypted at rest. We follow industry best practices for data security to protect your information.

While we implement strong security measures, we recommend not using Web Hook Box for highly sensitive data such as personal health information (PHI) or financial data unless you've implemented appropriate data filtering before sending webhooks to our service. For sensitive use cases, consider using our on-premises version.

1. Verify that you've correctly configured the webhook URL in the sending service
2. Check that your webhook URL is active in your Web Hook Box dashboard
3. Ensure the sending service is actually triggering webhook events
4. Look for any error messages in the sending service's logs or dashboard
5. Test your webhook URL with our built-in testing tool to confirm it's working properly

Check the following:

• Verify your forwarding URL is correct and accessible
• Check the webhook details page for any forwarding errors
• Ensure your endpoint accepts the HTTP method being used
• Examine if your endpoint expects specific headers or authentication that might be missing
• Use the replay feature to test forwarding with different configurations

You can report bugs or request features by creating an issue on our GitHub repository. For critical issues, please include steps to reproduce the problem and any relevant webhook IDs or screenshots.