Legacy Webhooks Deprecation - Flex Documentation
Why we’re making this change
To improve reliability, consistency, and future scalability, we’ve introduced a new webhook system in the Flex dashboard. The new system provides:
- Improved delivery reliability
- Consistent event payload structures
- Enhanced monitoring and debugging tools
- Support for more event types and filtering options
Migration timeline
| Date | Milestone |
|---|---|
| June 30, 2025 | Legacy webhook deprecation announcement |
| September 1, 2025 | Legacy webhook endpoints will be removed from the API |
How to migrate
Follow these steps to transfer your existing webhooks to the new system:
Access legacy webhooks
Visit the Legacy Webhooks page in the Flex dashboard to view your existing webhooks.
Document your current setup
Make note of the endpoint URL and subscribed events for each legacy webhook.
Navigate to the new webhooks page
Go to the Webhooks & Events page in the dashboard to begin recreating your webhooks.
Recreate each webhook
For each legacy webhook, create a new webhook using the same endpoint URL and event subscriptions.
Test and verify
Once your new webhooks are set up, test them to ensure events are being received correctly.
Remove legacy webhooks
After confirming your new webhooks are working properly, you must delete your legacy webhooks to avoid receiving duplicate events.
Important: If you don’t delete your legacy webhooks after migrating, your system will receive duplicate events which may cause issues with your integration.
Key differences to be aware of
The new webhook system is highly compatible with the legacy system. The only significant change is:
- Signature verification: The new system uses a different signature method
There are no changes to event names or payload structures, ensuring a smooth transition.
Need help?
If you have any questions or need assistance with migrating your webhooks, please contact us at support@withflex.com.