Before you connect
- Just your normal X login — no developer account or API keys of your own are needed.
How to connect X (Twitter)
- 1In SkedCast, go to Settings → Connections and click Connect X.
- 2Sign in to X and approve the requested permissions — see the exact scopes on the X integration page.
- 3SkedCast confirms the connection and shows your X handle and profile picture.
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.
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.