Connect X (Twitter)
A post with the article link, to the account the token belongs to.
What this key lets us do. It lets us post to that account. It cannot read your private messages or follow anybody on your behalf.
Step by step
- Go to developer.x.com and sign in with the account you want to post from. Create a project and an app inside it.
- In the app open User authentication settings and switch it on.
- Set App permissions to Read and write.
- Under Type of App choose one that suits you, fill in the callback and website fields as X requires, and save.
- Now request a user token with the scopes tweet.write, users.read and offline.access, and approve it as your own account.
- Copy the access token it returns.
Bold words are the exact buttons and menu names to look for. These are screens of other companies and they move them — if the layout does not match, searching that bold name in their own help usually finds where it went.
What to paste here
| Field | What it looks like |
|---|---|
| Access token | A long string; there is no separate account id to enter |
What usually goes wrong
- The bearer token on the app's Keys page is app-only. It can read, and X will refuse it for posting. It has to be a user token.
- Read permission alone is the most common mistake. It has to be Read and write, set BEFORE you generate the token — changing it afterwards means generating a new one.
- X's free tier limits how many posts a day an app may make. That limit is theirs; we report whatever they answer.
Whatever you paste is encrypted the moment it arrives. It is never shown back to you and nobody here can read it — support sees a fingerprint like “ending 7f3a2c”, never the value.
Stuck? The help desk answers this exact question, and it is a real answer rather than a form. Open the help desk → If you would rather go to the source, read the official documentation: X: OAuth 2.0 user access tokens