Frequently Asked Questions

EventForge is a webhook infrastructure platform that helps you log, monitor, replay, and route webhook events across your projects. It provides reliable webhook delivery with automatic retries, detailed logging, and powerful routing rules.

Most teams can set up EventForge and start receiving webhooks within minutes. Simply create an account, set up a project, and you'll receive a unique inbox URL to start receiving webhooks immediately.

Minimal changes are required. You simply point your webhook providers to your EventForge inbox URL instead of your direct endpoint. EventForge then forwards the webhooks to your actual endpoints based on your routing rules.

EventForge works with any programming language or framework. Since webhooks are HTTP-based, any system that can receive HTTP requests can work with EventForge. We provide examples for popular languages like Python, Node.js, Go, Ruby, and PHP.

EventForge automatically retries failed webhook deliveries using an exponential backoff strategy. All delivery attempts are logged, so you can see exactly what happened. Once your endpoint recovers, you can also manually replay any failed events.

Yes! Every webhook event is stored and can be replayed at any time within your retention period. This is useful for debugging, testing, or recovering from endpoint outages.

Routing rules let you filter and direct webhooks to different endpoints based on conditions like headers, path, or payload content. For example, you can route payment webhooks to one service and user webhooks to another.

Currently, EventForge focuses on reliable delivery, logging, and routing. Payload transformations are on our roadmap for future releases.

EventForge supports webhook payloads up to 5MB in size. Larger payloads will receive a 413 status code response.

Yes, security is a top priority. All data is encrypted in transit using TLS. Your webhook data is stored securely and isolated per project. We follow industry best practices for data protection.

Yes, webhook payloads are stored to enable features like event replay and debugging. Data is retained according to your subscription plan's retention period (7 days for Free, 30 days for Pro, 90 days for Enterprise).

No. Your webhook data is completely isolated to your account and projects. Each project has its own unique inbox URL, and only authenticated users with access to that project can view its events.

EventForge preserves all original headers including signature headers, so your endpoint can still verify signatures from the original provider. We pass through the webhook exactly as received.

Yes! Our Free plan includes 1 project, 1,000 events per month, and 7-day event retention. It's perfect for personal projects and testing.

Yes, you can change your plan at any time from your subscription settings. Upgrades take effect immediately, while downgrades apply at the end of your current billing period.

We accept all major credit cards (Visa, MasterCard, American Express) through our payment processor Stripe. Enterprise customers can also pay via invoice.

Refunds are handled on a case-by-case basis. If you're not satisfied with EventForge, please contact our support team and we'll work with you to find a solution.

We'll notify you when you're approaching your limits. If you exceed your monthly event limit, additional events will be queued and processed at the start of your next billing cycle. Consider upgrading to avoid interruptions.

EventForge accepts webhooks via POST requests. The original request method, headers, and body are preserved when forwarding to your endpoints.

We wait up to 30 seconds for a response from your endpoint. If your endpoint doesn't respond within this time, the delivery is marked as failed and will be retried according to the retry schedule.

Failed deliveries are automatically retried up to 5 times with exponential backoff (delays of approximately 1 minute, 5 minutes, 30 minutes, 2 hours, and 24 hours). You can also manually retry at any time.

Any 2xx HTTP status code (200-299) is considered successful. All other status codes trigger automatic retries.

Yes, EventForge supports both IPv4 and IPv6 connections for both receiving webhooks and delivering to your endpoints.

Yes! EventForge provides a REST API for programmatic access to your projects, events, and rules. API documentation is available at /api/v1 when logged in.

For Free and Pro plans, you can reach us via email at support@event-forge.app. Enterprise customers have access to dedicated support with faster response times.

Yes, comprehensive documentation is available in our docs section. We also provide integration examples, API references, and best practices guides.

Absolutely! We love hearing from our users. Send feature requests to feedback@event-forge.app and we'll consider them for our roadmap.