← back to Dear Bubbe Nextjs

GET_CORRECT_TOKENS.md

41 lines

# Getting the CORRECT X.com Tokens

## The tokens should look like this:

### auth_token (LONG - what you provided):
```
29242b900adcea897a68bf3c6f5ba838bc5b90ad2162404f2a02090757d7dd75042da41274308247b3296bd5cdfe262dee726059fcf260ea7caf13c41bb8bebf6f79acff9bb8b9dc6cdca30b0846bc65ec6f30c5212f03270cb1467cefbb5e44a9a18297
```
✅ This looks correct!

### ct0 (DIFFERENT, SHORTER):
The ct0 token should be:
- A DIFFERENT token (not part of auth_token)
- Usually 32-40 characters
- Looks like: `abc123def456...` (example)

## To find the REAL ct0:

1. Go to x.com
2. Open DevTools (F12)
3. Go to **Application** tab
4. Click **Cookies** → **https://x.com**
5. Look for a cookie named **ct0**
   - It should be DIFFERENT from auth_token
   - It's usually much shorter
   - It changes periodically

## Alternative way to get ct0:

1. In DevTools, go to **Network** tab
2. Post a tweet or like something
3. Look for any request to x.com/i/api/
4. Check the Request Headers
5. Find `x-csrf-token` - that's your ct0!

## Once you have the CORRECT ct0, run:
```bash
node /root/Projects/dear-bubbe-nextjs/lib/x-graphql-poster.js setup "29242b900adcea897a68bf3c6f5ba838bc5b90ad2162404f2a02090757d7dd75042da41274308247b3296bd5cdfe262dee726059fcf260ea7caf13c41bb8bebf6f79acff9bb8b9dc6cdca30b0846bc65ec6f30c5212f03270cb1467cefbb5e44a9a18297" "YOUR_REAL_CT0_HERE"
```

The ct0 should NOT be the same as auth_token!