Introducing Bob webhooks v2

Bob webhooks v2 is now available for use. It adds reliability and stability by reducing the data sent on the payload, ensuring the events will be sent in the correct order, and providing a better retry mechanism when a webhook fails to send the event.

What's new?

• We’ve made some structure changes to the payload format, and the payload now focus on metadata. Detailed data should be retrieved using Bob's API.
• We've revised the delivery mechanism and added email notifications in case of delivery errors. You can now set up the appropriate people to receive these notifications to address any issues proactively.

How does this affect me?

• No immediate action is required for organizations using Bob webhooks.
• When adding a webhook, you can choose between v2 (default) and v1.
• Webhooks v2 and v1 will run in parallel for now.
• For better reliability and stability, we recommend using Webhooks v2 for current and future integrations.

What's the timeline?

• Starting January 21, 2025, you can create v2 webhooks in Bob's UI.
• New v1 webhooks can still be created until April 1, 2025.
• From April 1, 2025, creating new v1 webhooks will no longer be possible.
• Existing v1 webhooks will continue to run alongside v2, but only v2 webhooks can be created after this date.
• Advance notice will be provided before any future deprecation of v1 functionality to ensure a smooth transition.

🚧

Deprecation notice:

Starting April 1, 2025, you will no longer be able to create new v1 webhooks in Bob's UI. We recommend reviewing the documentation and considering using v2 for your existing and future developments.

To learn more, see Migrate to webhooks V2.