Skip to content
  • There are no suggestions because the search field is empty.

How to Remove a Stale Webgility Webhook from Stripe for Webgility Online

This article explains how to identify and remove an outdated Webgility webhook endpoint from the Stripe Dashboard when repeated webhook delivery failure notifications occur with a 404 error, even though Stripe payment fees continue downloading successfully into Webgility Online. It provides steps to verify the Stripe connection, identify the obsolete endpoint, safely remove it, and confirm that payment fee downloads remain unaffected.

When Should You Use This Guide?

This guide applies when the following conditions are met:

  • You receive repeated webhook delivery failure notifications from Stripe.

  • The webhook URL contains webgility.com and the path /qapi/StripeWebhook/

  • The webhook delivery attempts return a 404 error.

  • Your Stripe payment fees are still downloading into Webgility Online successfully.

Why Is This Happening?

Stripe uses webhooks to send event notifications to connected applications. If a webhook endpoint is no longer active or supported, Stripe may continue attempting to deliver events to that endpoint, resulting in repeated delivery failure notifications.

Webgility Online downloads Stripe payment fees through its direct API connection rather than relying on this legacy webhook endpoint.

Therefore, if your Stripe connection is healthy and your payment fees are downloading correctly, removing the obsolete Webgility webhook should not affect the fee download process.

Steps to Remove the Outdated Webhook

Step 1: Verify Your Stripe Connection in Webgility Online

  • Log in to Webgility Online.

  • Navigate to Connections.

  •  

    Locate your Stripe connection.

  • Verify that the connection is present and does not display a connection error.

  • If your Stripe connection displays an error, resolve the connection issue before proceeding.


Step 2: Open the Stripe Dashboard

  • Log in to your Stripe account.

  • Navigate to Developers > Webhooks.

  • Review the list of configured webhook endpoints.

Step 3: Identify the Outdated Webgility Webhook

  • Look for webhook endpoints whose URLs meet both of the following conditions:

    • The URL contains webgility.com.

    • The URL path contains /qapi/StripeWebhook/

  •  

    There may be more than one matching endpoint. Verify each endpoint carefully before taking any action.

Step 4: Delete the Outdated Endpoint

  • Open the matching Webgility webhook endpoint.

  • Verify that the endpoint URL matches the criteria described above.

  • Click Delete endpoint.

  • Confirm the deletion if prompted.

Repeat these steps only for other endpoints that meet the same criteria.

Step 5: Verify the Results

After deleting the outdated endpoint confirm that the obsolete endpoint no longer appears in your Stripe webhook list. Continue monitoring Stripe for webhook delivery failure notifications. Verify that Stripe payment fees continue downloading into Webgility Online as expected.

Stripe notifications related to the deleted endpoint should stop once Stripe no longer attempts deliveries to it. Other webhook notifications may continue if they relate to different endpoints.