Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
AI connections and developer tools

Restore webhook delivery after rotating its signing secret

Update the receiver and verify the endpoint again with the replacement secret.

Updated 2026-11-11

In Webhooks, choose Rotate signing secret for the intended endpoint and read the credential confirmation. Save the replacement secret when it is shown once.

Update your receiver’s secure configuration before expecting signatures from the rotated endpoint to verify. The previous secret should not be treated as a permanent fallback after rotation.

Run endpoint verification again to resume delivery. Check the endpoint state and latest delivery result in developer settings. Retry failed deliveries is available only when the endpoint is active, so resolve verification before using that control.

Rotation does not rewrite existing resource records or make a missed notification equivalent to a missing import outcome. Poll the relevant resource while delivery is being restored and deduplicate any later replayed events. If you need help, share the endpoint ID and safe error details rather than the old or replacement secret. Disable endpoint is the separate action when delivery should stop altogether.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.