Conversation
The X API v2 bookmarks lookup endpoint (GET /2/users/:id/bookmarks) does not accept the literal string "me" as a path parameter — it requires the authenticated user's numeric user ID, which X rejects otherwise with a 400. The ID is already fetched and stored as x_oauth_user_id during the OAuth callback but was never read back in the fetch route. Fixes viperrcrypto#92 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
GET /2/users/me/bookmarksisn't valid for the X API v2 bookmarks lookup endpoint — it requires the authenticated user's actual numeric ID (GET /2/users/:id/bookmarks), which is why Live Import fails withX API error: 400right after a successful OAuth connect.x_oauth_user_idduring the OAuth callback; this reads it back and uses it in the bookmarks request URL.Fixes #92
Test plan
X API error: 400Found and fixed with the help of an AI coding assistant (Claude) while debugging my own local setup; verified working end-to-end before opening this PR.