[docs-agent] Add changelog Note for Alchemy Signer /signup deprecation#1389
Open
alchemy-bot wants to merge 3 commits into
Open
[docs-agent] Add changelog Note for Alchemy Signer /signup deprecation#1389alchemy-bot wants to merge 3 commits into
alchemy-bot wants to merge 3 commits into
Conversation
The /signup and /auth-jwt endpoints on api.g.alchemy.com/signer/v1 no longer accept new user signups or JWT-based wallet pregeneration as of June 16, 2026. Add a top-of-week Note pointing users at the Privy signer + Wallet APIs migration path. Refs DOCS-119 Requested-by: @avarobinson
🔗 Preview Mode
|
…ve date) Per Sahil in the Slack thread: date the Signer deprecation Note to today (the effective sunset date) instead of the upcoming Thursday. A separate weekly entry will follow on 2026-06-18. Refs DOCS-119 Requested-by: @avarobinson
…auth stay live Per Sahil's clarification in the Slack thread: the only endpoint going dark today is /signup. Login and auth endpoints (including /auth-jwt for existing-user authentication) remain live so existing users can continue to sign in and migrate. The previous Note conflated /signup and /auth-jwt as both being deprecated, which is wrong — /auth-jwt loses new-user signup and wallet pregeneration, but still authenticates existing users. Also rephrased the user-impact framing (new sign-ups will return an error) and the affected product surface (Alchemy Signer, Account Kit, Embedded Wallets) to match the internal cutover notice exactly. Refs DOCS-119 Requested-by: @avarobinson
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
<Note>block tocontent/changelog/2026-06-16.md(today, the cutover date) announcing the Alchemy Signer/signupendpoint shutdown. Mirrors the layout used for the legacyalchemyapi.ioshutdown notice incontent/changelog/2025-12-11.md.Scope is narrow: only
/signupis going dark today. New sign-ups for the Alchemy Signer / Account Kit / Embedded Wallets are no longer accepted and will return an error. Login and auth endpoints (including/auth-jwtfor existing-user authentication) remain live so existing users can continue to sign in and migrate to a new signer. Points readers at the Privy + Wallet APIs migration path and the signer migration overview (React + JWT / Auth0).A separate weekly entry will follow on the 2026-06-18 file (per Sahil in the thread).
Linear
DOCS-119 — https://linear.app/alchemyapi/issue/DOCS-119/add-changelog-entry-for-alchemy-signer-signup-endpoint-deprecation
Requested by
@avarobinson (via Slack thread)