docs: add missing Custom Webhook networks

[alchemy-bot]

Summary

• add 34 network identifiers missing from the create-webhook endpoint schema
• align the documented network enum with production chain configurations that support GRAPHQL Custom Webhooks

Verification

• confirmed all 34 added identifiers are present on the branch
• confirmed the enum contains 85 unique network identifiers

[github-actions]

🔗 Preview Mode

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	Sep 17, 2026, 6:59 PM

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bc6dca8e0d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Remove the retired Rinkeby network from the enum

When callers rely on the OpenAPI schema to select a Custom Webhook network, this advertises ETH_RINKEBY as valid even though the repository's current Ethereum guidance explicitly says Rinkeby was deprecated (content/tutorials/transactions/sending-transactions/how-to-send-transactions-on-ethereum.mdx:56). A retired network cannot provide the real-time activity promised by Custom Webhooks, so this value should not be added; the nearby legacy ARB_RINKEBY and OPT_KOVAN entries should also be rechecked before publication.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Do not restore Scroll Sepolia after its cutoff

For users generating or validating create-webhook requests from this schema, this once again presents SCROLL_SEPOLIA as supported. The history of this exact file shows that commit 04ac053 deliberately removed the same enum member as part of the post-cutoff Scroll Sepolia cleanup, so reintroducing it makes the Notify specification disagree with the supported network surface and directs callers toward a retired endpoint.

Useful? React with 👍 / 👎.