Connect X to Clone Social with your own X developer app
Create an app in the X Developer Console, set it up for OAuth 2.0 with Read and write access, and sign in to connect your X account.

Clone Social posts to X through your own X developer app. X charges per post, and those charges go to your X developer account, so you always see and control the cost. Setup takes about 10 minutes.
What you'll need
| You need | Why |
|---|---|
| The X account you want to post from | You sign in with it at the end. |
| An X developer account | Free to open at console.x.com with your X login. |
| Credits on your developer account | X's API is pay-per-use. You buy credits up front. |
| The owner or admin role in Clone Social | Only owners and admins can connect accounts. |
What it costs
X charges per action and bills your developer account directly. At the time of writing, X's published rates are:
| Action | X's price |
|---|---|
| A post | about $0.015 |
| A post that contains a link | about $0.20 |
A thread of five posts counts as five posts. Prices change, so check the current rates in your Developer Console before you start. Set a spending limit there to cap what you can spend per billing cycle. Clone Social itself adds nothing on top.
Step 1: Create your app
- Sign in at console.x.com.
- Accept the developer terms if asked.
- Click Create App (some accounts create a project first). Give it a name such as "Clone Social for Driftwood Coffee", a short description, and describe the use case, for example "Publishing our own posts and replies, scheduled by our team."
Step 2: Add credits and a spending limit
In the Developer Console's billing area, buy credits and set a spending limit per billing cycle. Without credits, X rejects posts.
Step 3: Turn on OAuth 2.0
In your app, open User authentication settings and click Set up (or Edit):
| Setting | Choose |
|---|---|
| App permissions | Read and write |
| Type of App | Web App, Automated App or Bot (a confidential client) |
| Callback URI / Redirect URL | https://social.clone.org/connect/oauth/callback |
| Website URL | Your company's website |
Click Save. The callback URL must match exactly, with no extra slash at the end. Clone Social shows the same address under Callback URL with a Copy button.
Step 4: Copy your OAuth 2.0 Client ID and Client Secret
After saving, X shows your OAuth 2.0 Client ID and Client Secret. Copy both now: X shows the secret only once. If you lose it, regenerate it under Keys and tokens.
Step 5: Connect in Clone Social
- Open social.clone.org (or ask your clone: "Open Clone Social") and go to Accounts.
- Under Add an account, find X and click Connect.
- Paste the OAuth 2.0 Client ID and OAuth 2.0 Client Secret.
- Click Continue to sign in.
- X opens. Make sure you're signed in as the account you want to post from, then click Authorize app.
- Back in Clone Social, tick the account in Choose the accounts Clone Social may use, click Add selected, then Done.
Clone Social asks X for these permissions when you sign in: tweet.read, tweet.write, users.read, media.write and offline.access. The last one lets Clone Social keep your sign-in fresh, so you don't have to reconnect every few hours.
Then click Settings on the account to set its approval and reply rules, and use the Team page to choose which clones may post to it.
What Clone Social can do on X
| X | |
|---|---|
| Posts | Text, threads, up to 4 images, or 1 video |
| Length | 280 characters per post. Every link counts as 23. |
| Replies | To people who @mentioned or quoted your account. Replies to your own posts (thread follow-ups, a first comment) are fine. |
About replies. Since February 2026, X only lets self-serve developer apps reply to posts that @mention or quote your account. Clone Social can't reply to other comments on X through the API; you'll need to answer those in the X app.
Keep your keys safe
- Encrypted and never shown again. Clone Social encrypts your Client ID, Client Secret and sign-in when you save them.
- Never handed to clones. Clones ask Clone Social to post; they never see your keys.
- Revoke any time. In X, go to Settings → Security and account access → Apps and sessions → Connected apps and revoke your app, or delete the app in the Developer Console.
- Don't paste keys into chat with anyone else. Paste them only into the Clone Social connect form.
- Exposed a secret? Regenerate it in the Developer Console and connect again.
Troubleshooting
"X says the app's account has no credits left." Your developer account is out of credits or hit its spending limit. Add credits or raise the limit in the Developer Console. Held posts can then be retried.
A reply fails with "X only lets apps reply to people who @mentioned or quoted this account". That's X's rule for self-serve apps (a 403 error). Answer that comment yourself in the X app. Replies to people who mention or quote you still work.
X shows an error before I can authorize (for example, something about the redirect or callback). The callback URL in User authentication settings doesn't exactly match https://social.clone.org/connect/oauth/callback. Fix it, save, and try again.
Posting fails with a permissions error, or X's sign-in page doesn't offer posting. The app is set to Read only. Change App permissions to Read and write, save, and connect again. Sign-ins made before the change keep the old permission.
"X refused the sign-in." Usually the Client Secret doesn't match the Client ID, or you chose a public client type. Make sure the app type is Web App, Automated App or Bot, copy both values again, and reconnect.
"Couldn't connect: the sign-in expired; try again." The X sign-in took longer than 10 minutes. Start again from Connect.
The account shows "This account needs to be reconnected." The sign-in was revoked in X or the app was changed. Posts are held, not lost. Connect again and they go out.
Still stuck? Open a support case. Never include your Client Secret in the case.
Related articles
Was this helpful?
Thanks. That helps us make this better.


