I received a webhook failure email from Chargebee. How to fix this?

Problem Statement

This article explains how to fix webhook failures when you receive error emails such as HTTP status code 200 not returned, 403 Authorization failed, or bad request from your server.

Related Scenarios

• Webhook URL returned HTTP status code other than 200
• Error code 403: Authorization failed (basic auth credentials)
• Invalid URL or handling code

Solution

These errors usually occur when the webhook credentials or endpoints in Chargebee are invalid or incorrect. Update the webhook settings in Chargebee.

Chargebee sends a daily summary email when webhooks fail.

Steps to Set It Up

1. Go to Settings > Configure Chargebee > API and Webhooks.
2. Click Webhooks.
3. Click the ... menu next to the webhook.
4. Click Update.
5. Enter the correct username and password.

For more details, see Webhook settings.

Important Notes

• When basic authentication for your webhook URL expires, you receive a webhook failure email. Update the webhook credentials in Chargebee.
• Webhook failures do not affect payments.
• Chargebee retries failed webhooks up to 7 times at exponential intervals.
• Webhooks are marked successful only when Chargebee receives a 2XX status code from your URL.
• For example, when a subscription_activated event occurs, Chargebee sends a JSON payload to your webhook URL. If the request times out, Chargebee cancels and retries.