Webhooks v2 will become the new default version
What’s changing?
From March 17, 2025, all new webhooks created via API will be version 2.0 by default. Until further notice, legacy v1 webhooks can still be created by specifying the version parameter in the API request body.
Why is it changing?
We introduced webhooks v2 at the beginning of 2023 to add reliability and stability by reducing duplicate and missing webhook triggers and delays. In addition, lead webhooks are supported in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.
I'm using webhooks v1, do I need to migrate to the new version?
Yes. Webhooks v2 and v1 will continue to run in parallel for now, but v1 will be deprecated entirely before the end of 2025. Please review the v1 to v2 migration guide closely, as there are significant differences in webhooks v2’s payload.
Comments
-
Hi @pieterh Pipedrive's Zapier app is unrelated to webhooks, but our team is aware of this and is already looking into the next steps in conjunction with Zapier. There’s no date for an update yet but keep an eye out here in the community for more updates.
1 -
Thank you Manuel. As a reference: There is polling ongoing in de Zapier app that uses 90k tokens a day, even if there are no Zaps triggered. Improving that will probably help you a lot in your infrastructure challenges!
To me, it would be sensible if the Zapier app would be improved before the new API usage rules kick in. I'm wondering if anybody else has this problem?
0
