| X | Telegram | |
|---|---|---|
| Characters | 280 | 4,000 |
| Media | optional | optional |
| Hashtags | 1-2 hashtags, zero is fine | not needed |
| Links in body | suppress reach | fine |
| Needs platform approval | yes | no |
X caps at 280 characters, Telegram allows 4,000. Posting the short version verbatim wastes the room Telegram gives you to actually explain the thing.
X: 1-2 hashtags, zero is fine. Telegram: not needed. Carrying the tag block across is the single most obvious sign of an automated cross-post.
X penalises links in the body, so posts written for it park the URL elsewhere. On Telegram links in the body are fine — putting it back is free reach.
X is one hook and nothing else — opinionated, conversational, over in a breath. Telegram is direct and clear; formatting is light. Those are different jobs, so the same words cannot do both well — and every algorithm here demotes text that obviously was not written for it. The fix is not to skip cross-posting; it is to send a native version to each network.
curl -X POST https://postwire.io/api/post \
-H "Authorization: Bearer $POSTWIRE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platforms": ["x", "telegram"],
"text": "Your post",
"per_platform": {
"x": { "text": "The X version" },
"telegram": { "text": "The Telegram version" }
}
}'
PostWire's /api/generate writes those per-platform versions for you from a single prompt, respecting
every limit in the table above. From an AI agent it is one MCP tool call.
Other pairs: Telegram to X · all combinations · which APIs need approval