Get channel posts (paginated)
telegram/web/channel-postsFetch a public channel's recent posts (text, photos, videos, forwards, replies, link previews, reactions, views, time).
- Base price
- $0.001USD / run
- Execution
- sync
- Model type
- api
- Input fields
- 4
Try the model
Playground
Input
Pagination cursor — fetch newer posts, pass `data.pagination.after_cursor` from the previous page.
Pagination cursor — fetch older posts, pass `data.pagination.before_cursor` from the previous page.
Channel username (required).
1100
Number of posts (1-100, default 20; when >20 the server automatically pages toward older posts). Range: 1 to 100.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
Specifications
Pricing
- Base price
- $0.001 / run
Context & modalities
- Supported modes
- sync
- Input
- Schema-defined
- Output
- api
Capabilities
- Chat
- Not supported
- Vision
- Not supported
- Reasoning
- Not supported
- Structured output
- Not supported
- Function calling
- Not supported
- Audio input
- Not supported
Access
- Provider
- Telegram
- Model ID
- telegram/web/channel-posts
- Execution
- sync
- API
- Platform API
- Endpoint
- /v1/api/telegram/web/channel-posts
API README
Get channel posts (paginated)
Fetch a public channel's recent posts (text, photos, videos, forwards, replies, link previews, reactions, views, time). It is suitable for telegram workflows.
Capability
Fetch a public channel's recent posts (text, photos, videos, forwards, replies, link previews, reactions, views, time). It helps applications, agents, and automated workflows turn that capability into repeatable tasks and useful downstream experiences.
Common use cases
- Build media monitoring, content intelligence, and publishing-support workflows.
- Create repeatable integrations that pass structured results to downstream business systems.
- Support scheduled jobs, internal tools, and agent workflows with structured results.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/telegram/web/channel-posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"after": 0,
"limit": 20,
"before": 0,
"channel": "telegram"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Choose your model
Compare models
| Model | Context | Input / 1M | Output / 1M | Released |
|---|---|---|---|---|
Get channel posts (paginated)This model Telegram | — | — | — | Jul 31, 2026 |
Telegram | — | — | — | Jul 31, 2026 |
Telegram | — | — | — | Jul 31, 2026 |
Telegram | — | — | — | Jul 31, 2026 |
Telegram | — | — | — | Jul 31, 2026 |
Telegram | — | — | — | Jul 31, 2026 |
