Skip to content
SkedCast
Start free

Help Center

Connect your X (Twitter) account to a social media scheduler (and fix connection problems)

Connect your X (Twitter) account to SkedCast, a social media scheduler, in a few steps. Connecting X is a standard OAuth 2.0 sign-in — you don’t need your own X developer account, since SkedCast holds the registered app. The permissions requested cover posting, media uploads, and the background access needed to publish on schedule.

All connection guides

By Angelina F. · Updated

Before you connect

  • Just your normal X login — no developer account or API keys of your own are needed.

How to connect X (Twitter)

  1. 1In SkedCast, open Connected Accounts, choose Connect, then X (Twitter) — or send the account owner an invite link to connect it themselves.
  2. 2Sign in to X and approve the requested permissions — see the exact scopes on the X integration page.
  3. 3SkedCast confirms the connection and shows your X handle and profile picture.

What can you publish to X (Twitter) once it is connected?

  • A caption of up to 280 characters, with or without media.
  • Images: up to 4 per post, JPG, PNG, WEBP, GIF, up to 5 MB each.
  • Video: one per post, MP4, MOV, up to 512 MB each, up to 140 seconds long.
  • GIFs: one per post, GIF, up to 15 MB each.
  • Alt text on images, written in the composer.
  • A first comment, published right after the post.
  • Scheduling by SkedCast, which holds the post and publishes it at the time you set.

Common connection problems

Posts stop publishing with a permissions or scope error.
X ties specific permissions (posting, media uploads, and background/offline access for scheduled publishing) to the consent you originally gave. If SkedCast’s requested permissions changed since you first connected, your existing token won’t automatically pick up the new ones — reconnect to re-consent.
Media (images/video) won’t upload even though text posts work.
Uploading media needs its own permission on top of basic posting. If your account was connected before that permission was requested, reconnect to grant it.
A post looks like it failed, but it actually went out (or the reverse).
X occasionally returns an ambiguous response that could mean the post published or didn’t. SkedCast never silently retries in that situation, to avoid posting the same thing twice — check your X profile directly before manually reposting.
Permissions & OAuth scopes for X (Twitter)How to post on X (Twitter)
X (Twitter)account connectiontroubleshooting

FAQ

Do I need my own X developer account to connect?
No. SkedCast’s registered X app handles the developer side — you only need to sign in with your regular X account and approve the connection.
Why did X disconnect after working fine for a while?
The most common cause is a permissions/scope mismatch after an update to what SkedCast requests, or the connection being revoked from X’s own Connected Apps settings. Reconnecting re-establishes it either way.
Can a client connect their own X (Twitter) account without sharing a password?
Yes. Send the account owner an invite link from SkedCast. They sign in to X (Twitter) themselves and approve the connection, so their password never leaves their hands and you can start scheduling once it is connected.
What happens to scheduled posts if the X (Twitter) connection breaks?
They cannot publish until the account is reconnected. SkedCast shows each connection’s health and offers a one-click reconnect; after reconnecting, retry any post that failed in the meantime.
Can I connect more than one X (Twitter) account?
Yes. Connect each account separately; they all count toward your plan’s connected-account limit, and you can group them by client so each client’s posts stay apart.

More on this topic

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.

Start freeLog in to your console