Publishing API

Telegram publishing API with one SocialClaw workspace.

Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use. SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets.

Try the CLI Open dashboard

Account type Bot-connected channel, group, supergroup, or chat Telegram supports text-only posts or one image or one video per post.

Best fit AI agents Telegram does not use OAuth in SocialClaw.

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Account target Bot-connected channel, group, supergroup, or chat SocialClaw supports Telegram text messages, text plus one image, or text plus one video through bot-connected targets.

Auth model Manual connect Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.

Media envelope Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.

Inspection Validate, apply, inspect Analytics snapshots are available, but Telegram provider-native analytics are not implemented. Telegram reconciliation is not implemented yet.

What the payload needs

The main fields and constraints to account for.

Bot-connected channel, group, supergroup, or chat stored in the SocialClaw workspace
Telegram supports text-only posts or one image or one video per post.
Provider-specific settings such as parseMode, disableNotification, protectContent, disableLinkPreview
Workspace API key auth and post or run inspection after apply

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Authenticate the workspace

Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.

Step 2

Connect Telegram

Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.

Step 3

Inspect account capabilities and settings

Read the current settings surface, including parseMode, disableNotification, protectContent, disableLinkPreview, before generating the final payload.

Step 4

Validate before apply

Validation should happen before create-run or apply. Telegram supports text-only posts or one image or one video per post.

Step 5

Inspect the resulting run or post

Telegram reconciliation is not implemented yet. Analytics snapshots are available, but Telegram provider-native analytics are not implemented.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow Telegram publishing API

socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider telegram --bot-token <bot-token> --chat-id @yourchannel --json
socialclaw accounts capabilities --provider telegram --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json

HTTP API flow Hosted SocialClaw endpoints

curl -sS \
  -H "Authorization: Bearer $SC_API_KEY" \
  "https://getsocialclaw.com/v1/keys/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"telegram","botToken":"<bot-token>","chatId":"@yourchannel"}' \
  "https://getsocialclaw.com/v1/connections/start"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/validate"

curl -sS \
  -X POST \
  -H "Authorization: Bearer $SC_API_KEY" \
  -H "Content-Type: application/json" \
  -d @schedule.json \
  "https://getsocialclaw.com/v1/posts/apply"

Current limitations

A few practical limits to keep in mind.

Telegram does not use OAuth in SocialClaw.
Channels require the bot to be an administrator or creator.
Replies and threaded Telegram interactions are not implemented.

Related routes

Related integrations and use cases.

Integration

Telegram SocialClaw keeps Telegram bot connection, schedule validation, media delivery, and publishing state in one workspace instead of requiring the bot token in every script.

Use case

AI agents Use one SocialClaw workspace for AI-agent account connection, hosted media handoff, validation, apply, and publish inspection.

Product

Pricing Trial and plan details for CLI or API execution

Product

AI agents overview Main SocialClaw page for AI-agent publishing

Frequently asked questions

What account type does the Telegram publishing API route use?

Telegram uses the Bot-connected channel, group, supergroup, or chat route in SocialClaw. Telegram is connected manually with a bot token and a numeric chat id or @channel username, then stored in the SocialClaw workspace for later CLI or API use.

What media rules apply to the Telegram publishing API route?

Telegram supports text-only posts or one image or one video per post. Telegram fetches the public image or video URL during publish.

What should the workflow inspect before applying Telegram posts?

Inspect settings such as parseMode, disableNotification, protectContent, disableLinkPreview and capabilities. Telegram does not use OAuth in SocialClaw.

Run the Telegram publishing API workflow in SocialClaw

Connect the account once, validate before publish, and keep everything in one workspace.

Try the CLI Open dashboard