Scheduling to Telegram through SkedCast's API#
SkedCast's /v1 REST API schedules text, photo, video, and document posts to Telegram the same way it does every other platform: one POST https://api.skedcast.com/v1/posts call with a content caption and a targets block naming the connected accounts. You need a Telegram bot added as an admin of the channel, connected once through the console (or minted as a self-serve connect link via POST /v1/clients/:id/connect-invites).
SkedCast is not a raw wrapper over Telegram's own developer API — it is one versioned, platform-agnostic contract that fans a single compose call out across every connected network, with the Telegram-specific fields listed below folded into the same request shape.
Telegram-specific fields (`variants[].overrides.telegram`)#
| Field | Notes |
|---|---|
chatId | Optional when the account was connected to a channel on or after 2026-09-05 (the row's own chat id is the destination). **Required** for an account connected before that date, or one bound to a bot rather than a specific channel. |
Example: schedule a post to Telegram#
{
"clientId": "…",
"content": "New build is out — changelog in the pinned message.",
"targets": { "mode": "accounts", "accountIds": ["…"] },
"schedule": { "type": "at", "at": "2026-10-01T09:00:00" },
"variants": [
{ "platform": "telegram", "overrides": { "telegram": { "chatId": "-1001234567890" } } }
]
}Telegram facts#
| Fact | Value |
|---|---|
| Max caption length | 4,096 characters |
| Media per post | 10 media item per message via our adapter today. |
| Native platform scheduling | No — SkedCast's managed engine holds the timer |
| SkedCast's default pacing | No default daily cap; ~30s spacing per account |
Published-post URL (permalink) | https://t.me/{channel}/{id} for a public channel; https://t.me/c/{internal}/{id} for a private channel or supergroup (access-gated — resolves for members, which is everyone the post was for). A plain group or DM yields no link. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/:id returns the Telegram target's status (scheduled, published, failed, …), plus error, statusReason, and retryAt when it's parked waiting on something — SkedCast's own pacing, a platform rate limit, or media still transcoding, each with its own machine-readable reason. Once published, externalId and permalink (see the table above) point at the live post.
- Subscribe to
target.published/target.failedwebhooks (or the legacypost.*pair) instead of polling — see [Webhooks](/developers/webhooks). - Or connect an MCP client and ask an agent to check — see [Connect an AI agent](/mcp).
FAQ
- What can I schedule to Telegram through the API?
- Telegram posts of type: text, photo, video, and document posts, via one `POST https://api.skedcast.com/v1/posts` call — the same endpoint used for every other connected platform.
- How do I authenticate against the Telegram API endpoint?
- The same way as every `/v1` route: an API key (`Authorization: Bearer sked_live_…`) or an OAuth 2.1 bearer token, scoped to `posts.compose` to schedule and `posts.read` to read back status. See Authentication.