X (Twitter)

Publish tweets, threads, and media to X. Postli uses the X API v2 with OAuth 2.0 PKCE. Replies and self-threading are supported; quote-tweets and DMs are not.

Requirements

• An X account in good standing — suspended or shadow-restricted accounts may publish but lose engagement read.
• An X developer account on a paid tier (Basic or higher) — tweet publishing is not available on the free tier. You will create your own app and paste the credentials into Postli; see Create your X developer app below.
• For long-form posts (>280 characters): X Premium on the connected account.

Spec

Create your X developer app

X requires merchants to bring their own API credentials — the app you build sits under your X developer account, with its own quota and pricing tier.

1. Sign in at developer.x.com/en/portal/dashboard. If you don’t have a developer account yet, apply — approval is usually instant for paid tiers.
2. Create a Project, then a App inside it. The Project lets you upgrade to higher tiers if you ever need them.
3. Open User authentication settings on the app. Choose:
   • App permissions: Read and write
   • Type of App: Native App — not Web App, Automated, or Bot (those break OAuth 2.0 PKCE and fail with error 32)
4. Add the Callback URI:
   https://app.usepostli.com/api/integration/twitter/callback
   Set Website URL to your store domain. Save.
5. Under Keys and Tokens, generate (or regenerate) the OAuth 2.0 Client ID and Client Secret. Save them somewhere private — the secret is shown only once.
6. In Postli, open Settings → Integrations → X (Twitter), paste the Client ID and Secret, save.

OAuth setup

Once credentials are saved, go to Integrations → X → Connect. You’ll be sent to X’s OAuth 2.0 consent screen. After approval, Postli stores the access and refresh tokens.

Scopes Postli requests:

Post types in detail

Tweet

Single 280-character tweet (or up to 25,000 for Premium accounts — Postli detects which based on the API response). Up to 4 images, or 1 video, or 1 GIF.

Thread

Use + Add tweet on the X channel tab to chain tweets as a self-reply thread. Each tweet in the thread has its own character count; Postli enforces the limit per tweet, not across the thread.

Auto-reply (auto-comment)

Postli implements auto-comments on X as a self-reply tweet to the published parent. Instant and Time conditions both work; LikeCount uses the like metric returned by the v2 metrics endpoint.

Rate limits

X API v2 rate limits depend on the access tier and endpoint. For posting tweets via OAuth 2.0 user context, the typical limit is 200 tweets per 15-minute window per user. Media upload limits are separate. Postli back-offs and retries on 429 with exponential delay.

Gotchas & best practices

• Long posts need Premium. If the account is not Premium, anything over 280 characters will fail with a 422. Postli surfaces the error on the post detail.
• One media-type per tweet. You cannot combine images and video, or images and GIF, in the same tweet.
• Quote-tweet is not supported. The v2 publishing endpoint does not currently expose quote_tweet_id for OAuth 2.0 user context.
• URL counts as 23 characters. X auto-shortens links to t.co; even a long Postli URL counts the same.
• Token refresh. Tokens expire after 2 hours. Postli’s scheduled token-refresh job rotates them ahead of expiry; if a refresh fails (e.g. user revoked from X settings), an account-health alert fires.

Webhooks

Postli does not subscribe to X webhooks (Account Activity API requires a separate access tier). Engagement metrics are polled.