If you configured webhooks before August 31, 2026, your endpoints still work, but you need to migrate them before October 2026.
Before Migrating
If you had set up a whitelist of authorized IPs for checking the webhook's origin IP, you need to update it.
- Legacy webhooks are sent from :
- 34.65.253.117
- 34.65.146.131
- New webhooks are sent from :
- 52.215.16.239
- 54.216.8.72
- 63.33.109.123
- 2a05:d028:17:8000::/56
Option A: Migrate automatically
- In Settings › Integrations, open Incoming faxes (Legacy) or Outgoing faxes (Legacy) and click Migrate Now.
- We recreate all of your legacy endpoints, incoming and outgoing, in the new panel in a single click.
What stays the same
- Your endpoint URLs are copied across as-is.
- Payload format is unchanged, so your existing parser keeps working.
- Your per-number filters are preserved.
- No downtime: events keep flowing throughout.
What changes
- Events are sent from new source IP addresses.
- Requests now carry a signature header you can verify for increased security.
- Your legacy endpoints are removed once the migration succeeds.
- You can no longer create legacy endpoints.
Option B: Migrate manually
- If you prefer, you can also execute the steps by yourself :
- First, recreate the endpoints in the new configuration panel.
- Once you have tested and verified that the new events are received correctly, then you can delete the legacy endpoints. (Note: If you keep both the new and old configurations, you will receive two webhooks for the same event.)