Tweets
Publish tweets with automatic format detection
Publish tweets to X (Twitter) with automatic format detection. Handle images, videos, and text posts seamlessly.
One API call handles tweets with automatic content format detection.
Publish tweets with automatic format detection
Add up to 4 images or 1 video per tweet
Create threaded conversations with multiple tweets
Content format determined automatically based on media
curl -X POST "https://api.postproxy.dev/api/posts" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "post": { "body": "Just shipped a new feature! Check it out 🎉" }, "profiles": ["twitter"], "media": ["https://example.com/image.jpg"], "platforms": { "twitter": {} } }'| Format | Description |
|---|---|
post | Tweet (default) |
| Media Type | Max Size | Formats | Max Count | Duration |
|---|---|---|---|---|
| Image | 5 MB | jpg, png, webp, gif | 4 | - |
| Video | 512 MB | mp4, mov | 1 | 1s - 140s |
View full documentation for all platform-specific features for X (Twitter)
No need to handle Twitter API v2, OAuth flows, or rate limits. Postproxy handles it all.
Twitter rate limits are managed automatically with intelligent retry logic.
Publish tweets with text, images, or videos through one unified API.
Automatic retries and clear status reporting ensure your tweets reach X.
X (formerly Twitter) uses a v2 API that requires OAuth 2.0 with PKCE for user-context authentication. Publishing a tweet is a single POST request, but media attachments require a separate multi-step upload flow through the v1.1 media endpoint — the v2 API still relies on v1.1 for media uploads. Postproxy handles this split: send your text and media URLs in one request, and the API manages the v1.1 media upload followed by the v2 tweet creation automatically.
X's media upload endpoint uses a chunked upload protocol for videos and GIFs over 5MB. Each chunk must be uploaded sequentially, with a finalize step at the end and optional status polling for async video processing. Images are simpler but still require a separate upload-then-attach flow. Postproxy detects the media type from your URLs, chooses the correct upload method, handles chunking for large files, and attaches the resulting media IDs to your tweet.
X has some of the strictest rate limits of any social platform — as low as 17 tweets per 24-hour window on free-tier API plans, with separate limits for media uploads. The API also has a 280-character limit for tweet text (with URLs counting toward the limit differently than plain text). Error responses from X are often vague, returning generic 403s for multiple distinct issues. Postproxy validates content length, manages rate limit windows, and translates X's error codes into actionable messages.
Posting a thread on X requires creating each tweet sequentially, with each reply referencing the previous tweet's ID. If any tweet in the chain fails, you're left with a partial thread. Postproxy's thread support lets you send an array of tweet contents and handles the sequential posting with proper reply chaining, rolling back on failure so you don't end up with orphaned partial threads.
Common questions about X (Twitter) integration
Start with our free plan and scale as your needs grow. No credit card required.