How to migrate webhooks to a new Alchemy account with minimal downtime

If you need to move your webhooks to a different Alchemy account or team (for example, after an account or organization change), you have two options for handling the migration.

Option 1: Recreate webhooks in the new account, then switch over

This approach lets you get webhooks fully set up in the new account before switching production traffic, so you control exactly when the cutover happens.

1. For each existing webhook, use the webhook addresses endpoint to retrieve the full list of addresses it is tracking. You may need to paginate through the results.

2. Recreate each webhook in the new account.

3. Add the saved list of addresses to each corresponding new webhook.

4. Update your application to point at the new webhook's signing key and auth token.

Because both sets of webhooks can exist at the same time, this path can be done with zero downtime if you finish setting up and verifying the new webhooks before disabling or deleting the old ones.

Option 2: Move existing webhooks directly to the new account

If your webhooks are moved directly into the new account rather than recreated, the amount of downtime depends on how quickly you can update the auth token your application expects. As soon as the webhooks are moved, Alchemy starts signing payloads with the new account's auth token, and any payload your system checks against the old token will be rejected.

To minimize the disruption:

• Have your new auth token ready in advance and update your production environment as close as possible to the same time the webhooks are moved.

• Expect a brief window (potentially a few seconds) where payloads may be rejected while the swap is in progress.

• Coordinate directly with your Alchemy contact to schedule the move, so both sides are ready to act at the same time and the rejection window is kept as short as possible.

If you have questions about migrating your webhooks, reach out to support@alchemy.com.