What is changing?
From March 17, 2025, all new webhooks created via API will be version 2.0 by default. Legacy v1 webhooks can still be created by specifying the version parameter in the API request body until further notice.
Why is it changing?
We introduced webhooks v2 at the beginning of 2023 to bring added reliability and stability by reducing duplicate and missing webhook triggers and delays. In addition, lead webhooks only exist in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.
Things to know about webhooks v2
- Webhooks v2 and v1 will continue to run in parallel for the time being but v1 will be deprecated completely by the end of 2025. You will be notified of any changes via our Changelog, so make sure you subscribe to it.
- Please review the v1 to v2 migration guide closely as there are significant differences in webhooks v2’s payload.
- Should a field no longer be available in the payload of a v2 webhook, please query it from our API.
Learn about webhooks v2 here and how to migrate your webhooks from v1 to v2 here. If you have any feedback or run into any issues, please do let us know in our Developers’ Community!