Repository navigation
docs(wallets): document that Wallet API call IDs are opaque - #1691
Merged
Merged
Conversation
Call IDs were never described as opaque or format-unstable, so users may be parsing them. Add guidance not to depend on their structure. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔗 Preview Mode
|
jakehobbs
marked this pull request as ready for review
October 8, 2026 03:35
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
inakov
approved these changes
Oct 8, 2026
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
2 participants
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.
Description
The docs never said what a Wallet API call ID is made of or that its format is not guaranteed, so users may be parsing it. This adds guidance that call IDs are opaque and should only be passed back to Alchemy APIs.
Related Issues
None.
Changes Made
debug-transactions/index.mdx: expanded the Call ID bullet to say IDs are opaque, shouldn't be parsed, and may change format without notice.smart-wallets/quickstart/api.mdxandsdk.mdx: added a<Note>after the step where the call ID is first returned.Testing
Docs-only change; I have not run the validation scripts or a docs build, and haven't checked how the
<Note>callouts render.pnpm run validate)🤖 Generated with Claude Code