Skip to main content

Connecting X (Twitter)

X's developer portal (developer.x.com; some pages and documentation still live under the older developer.twitter.com branding) uses a Project → App structure. Setup itself is short — the main thing to get right is the app permissions and the callback URI.

1. Create a Project and an App​

  1. Go to developer.x.com and sign in with your X account (apply for developer access first if you haven't already).
  2. Create a Project.
  3. Inside that Project, create an App.

2. Configure User authentication settings​

  1. Open the App's User authentication settings and click Set up.

  2. Enable OAuth 2.0.

  3. Under App permissions, choose Read and Write — Stitchable needs write access to post on your behalf; the default read-only permission will not work.

  4. Under Type of App, choose whichever fits how you want to run this:

    • Confidential client (Web App, Automated App, or Bot) — has a client secret. Paste both Client ID and Client secret into Stitchable.
    • Public client (Native App) — no client secret, uses PKCE alone. Leave Stitchable's Client secret field blank and click Skip on that step.

    Stitchable supports either; it only sends a client secret to X if you actually gave it one.

  5. Set the Callback URI / Redirect URL to http://127.0.0.1.

  6. Save your changes.

Unverified: X may require an exact port match

Stitchable's local OAuth callback binds a freshly-chosen port each time you connect — it can't register one fixed value ahead of time. X's own developer documentation states callback URLs "must match exactly," and unlike TikTok (which documents an explicit * wildcard-port option), no equivalent wildcard has been confirmed for X as of this writing. This step has not yet been tested against a live X app. If sign-in fails with a callback/redirect URI mismatch, this exact-port requirement is the likely cause — X's loopback OAuth would need a fixed local port (the same fix Instagram's connector already uses) rather than Stitchable's current freshly-chosen one.

3. Copy your credentials​

Go to the Keys and tokens tab and copy the OAuth 2.0 Client ID (and Client Secret, if you chose a Confidential client type in step 2).

4. Connect it in Stitchable​

  1. Open the connect wizard from the Publishing page and choose X.
  2. Paste the Client ID (and Client secret, if you have one) from step 3.
  3. Click Save & continue (or Skip if you're using a Public client with no secret).
  4. Click Sign in with X. A browser window opens X's real sign-in and authorization screen.
  5. Log in and click Authorize app.

The wizard finishes automatically once you approve.

Free-tier limits

X's free and basic API tiers carry real rate limits and monthly posting caps that vary by account age and tier, and are documented inconsistently across sources. If posts unexpectedly fail during testing, check your tier's current limits in the Developer Portal before assuming Stitchable is the problem.