X Setup — API tokens or browser session
Same two-path model as Instagram: API tokens for production, browser session for quick start.
Path A — X API v1.1 (OAuth 1.0a)
Step 1 — Developer account
- Sign up at developer.x.com
- Create a Project → inside it, create an App
- App Permissions — select Read and Write (or Read+Write+DM if you want DMs)
Step 2 — Generate keys
- App → Keys & Tokens
- Under Consumer Keys: copy API Key and API Secret
- Under Authentication Tokens: generate and copy Access Token and Access Token Secret for your account
Step 3 — Connect in Limaze
- Integrations → X card → Connect via API
- Paste all 4 values: App Key, App Secret, Access Token, Access Secret
- Limaze validates by fetching your account handle
Path B — Browser session
Setup
- Integrations → X card → Connect via browser session
- Log in to X in the opened window
- Confirm your account handle in Limaze
Browser sessions work for basic posting but don't expose full metrics API.
Limits to know
- X free tier API allows 1500 tweets/month — enough for most single-account studios
- Thread length: standard 280 chars per tweet, unlimited tweets per thread (but practically <10)
- Media: images, GIFs, short video (up to 140s)
Tools lims get
x_post— single tweetx_thread— multi-tweet threadx_post_metrics— impressions, likes, replies, quotes, bookmarks per tweet
Troubleshooting
- "Read-only application" — your App's permissions are Read-only. Change to Read+Write in developer portal, regenerate Access Token, paste new one into Limaze
- Rate limited — X free tier is aggressive. Drop posting cadence below 1/hour to stay safe
