Github App - Clarification Needed on Updating Webhook URL for Existing GitHub App

[gouravjblackduck]

Select Topic Area

Question

Body

Hello GitHub Team,

We are planning to update the webhook URL for one of our existing GitHub App, and I would like clarification on a few points before proceeding:

Do we need any approval from GitHub to change the webhook URL of an existing GitHub App, or can this update be made at any time by the app owner?

Are there any known issues or risks associated with updating the webhook URL on an older GitHub App?
For example, will existing installations or event deliveries be affected during the transition?

Is it recommended to keep the old service running temporarily and forward webhook traffic to the new service until the change fully propagates?
If so, is there any best‑practice guidance for handling this migration?

After updating the webhook URL, how long does it typically take for the new URL to take effect for all webhook deliveries?
Is the change immediate, or is there a propagation delay?

Any guidance or recommendations you can provide would be greatly appreciated.

Thank you.

[itsmohitkala]

We’ve done this in production a few times, and it’s pretty straightforward.

You don’t need any approval from GitHub — the app owner can update the webhook URL anytime from the GitHub App settings. Existing installations stay intact.

What we’ve seen in practice

• New webhook deliveries start hitting the new URL almost immediately

• There’s no dual delivery, so if the new endpoint isn’t ready, events can fail
  (GitHub retries for a limited time, but not indefinitely)

• We usually keep the old service running briefly and either forward traffic or monitor deliveries until everything is stable

Tip :-

Keep an eye on the Recent Deliveries section after the change — it’s the fastest way to confirm things are working and catch failures early.

Official docs we’ve followed

• GitHub App webhooks

• Modifying a GitHub App

• Webhook retries & troubleshooting

Overall, it’s a low-risk change as long as you allow a short overlap and keep an eye on deliveries 👍

[gouravjblackduck]

Thank you for the quick reply and clarification on the webhook URL update.

I have one additional question: would the same process and considerations apply if we update the callback URL of our GitHub App? Specifically, is there any approval required for that and propagation time, or best practices we should follow to do that also ?
I think we can have multiple callback URL so it should not any issue if we add another callback

[mehmadullahsheikh]

You do not need any approval from GitHub to change the webhook URL. The app owner can change it anytime from the app settings.

Here is what happens when you change it:

Existing installations are not affected.
Your app will stay installed on all repositories.

The change works almost immediately.
New webhook events will start going to the new URL within seconds.

There is a small risk of missing events if the new server is not ready or is down at the time of the change.

Best way to do the change (recommended):

Set up and test the new webhook endpoint first.

Make sure it can receive and process GitHub webhooks.

Change the webhook URL in the GitHub App settings.

Watch the delivery logs to confirm everything is working.

Keep the old service running or forwarding requests for a short time just in case.

Turn off the old service after you confirm the new one is stable.

Summary

No GitHub approval needed

Installations stay the same

Change takes effect immediately

Risk only if new endpoint is not ready

Safe if you follow the steps above

[gouravjblackduck]

Thank you for the quick reply and clarification on the webhook URL update.

I have one additional question: would the same process and considerations apply if we update the callback URL of our GitHub App? Specifically, is there any approval required for that and propagation time, or best practices we should follow to do that also ?
I think we can have multiple callback URL so it should not any issue if we add another callback