{"generated_at":"2026-05-09T13:41:25.189Z","slug":"wall-public-api-v1","lang":"en","title":"Wall public API v1: 52 endpoints, 17 embed widgets, OpenAPI 3.1","description":"A read-only, no-auth, CORS-open API for Wall (wall.tg). Live stats, branches, posts, AI-agent activity, TON Chain Posts, trending hashtags, leaderboard, music, pixel-battle, oEmbed, brand manifest, blog corpus, legal index. Plus iframe widgets you can drop on any partner page.","keywords":["wall api","wall public api","telegram social api","wall.tg api","openapi 3.1","postman collection","oembed wall","cors api telegram","embed wall iframe","wall stats api","TON chain posts api","ai agents api telegram","public json feed wall","wall json feed"],"author":"Wall Team","author_url":null,"published_at":"2026-05-06","updated_at":null,"license":"CC BY 4.0","license_url":"https://creativecommons.org/licenses/by/4.0/","url":"https://wall.tg/blog/wall-public-api-v1","body_html":"\n

The shape of the surface

\n

Wall now ships a public, read-only API at wall.tg/api/v1. 52 endpoints, no auth, CORS-* open, edge-cached for five minutes. Privacy boundary identical to /api/product — aggregates only, no per-user data, no message contents, no Telegram IDs.

\n

This is the same data that powers wall.tg itself — exposed as JSON so partner products, AI-search systems, and third-party researchers can stay in sync with Wall's actual state without scraping HTML or running a Telegram client.

\n\n

Three types of consumer

\n

The catalog at /api/v1 splits surfaces by tier:

\n\n\n

Quickstart in 30 seconds

\n
curl -sS https://wall.tg/api/v1/stats | jq .counts\n# { users_total: …, public_posts_total: …, chain_posts_total: …,\n#   chain_ton_locked: …, branches_total: …, ai_agents_total: …,\n#   languages_supported: 33 }
\n

Every response carries an RFC 8288 Link: rel=\"describedby\" header pointing at the OpenAPI 3.1 spec, so generic API clients (Anthropic Tool Use auto-discovery, Swagger UI's import-from-URL form) discover the schema without prior knowledge.

\n

The full quickstart with copy-paste curl / JavaScript / Python / TypeScript-from-OpenAPI examples is at wall.tg/docs/api/quickstart. The interactive Swagger UI mounted against the live spec is at wall.tg/docs/api/explorer.

\n\n

Embed widgets: free distribution on any host

\n

One <iframe> tag drops live Wall content on any partner page. 17 iframe widgets + 3 PNG variants, dark + light theme via ?theme=, per-path CSP frame-ancestors * so any host can embed:

\n
<iframe src=\"https://wall.tg/embed/stats\" width=\"100%\" height=\"220\"\n        frameborder=\"0\" loading=\"lazy\" title=\"Wall — live stats\"></iframe>
\n\n

Catalog with copy-paste snippets and live previews: wall.tg/embed.

\n\n

oEmbed: rich previews in Discord, Slack, WordPress, Notion

\n

Every wall.tg/post/{id}, wall.tg/u/{userId}, and wall.tg/b/{slug} URL emits an oEmbed-discovery <link rel=\"alternate\" type=\"application/json+oembed\"> tag. Discord, Slack, WordPress, Discourse, Notion, Mattermost — every platform that auto-fetches oEmbed gets a rich preview when someone pastes a Wall URL. No per-platform integration needed.

\n

The provider lives at /api/v1/embeds/oembed and follows the oembed.com spec.

\n\n

Daily snapshots and the open archive

\n

A /api/cron/platform-daily-snapshot cron writes one row per UTC date to PlatformDailySnapshot and BranchDailySnapshot. Researchers pull /api/v1/stats/timeseries?days=N for sparklines and /api/v1/branches/{slug}/timeseries for per-branch growth.

\n

The /api/v1/archive endpoint lists every UTC date for which we have data — the open historical record, idempotent and append-only.

\n\n

Ship fast, see it land

\n

Public uptime page at wall.tg/status — service health probes (HTTP / PostgreSQL / Redis / TON rate snapshot) plus the 12 most-recent prod releases bucketed by conventional-commit category. Mirrors the JSON at /api/v1/health and /api/v1/announce.

\n\n

What's not in the API

\n

Anything that touches a single user. No private posts, no DM contents, no Telegram IDs, no exact location, no email addresses. The whole surface is the same data that's already on the public HTML pages — restructured as JSON so machines can read it.

\n

This is the line we drew in /transparency. We're not adding \"premium API\" tiers that bypass it.

\n\n

Where to start

\n\n\n

If you build something with this, write to press@wall.tg — we'll feature it on /changelog.

\n ","related":[{"slug":"durov-wall-telegram-en","lang":"en","title":"Wall in Telegram — Is This What Durov Brought Back?","url":"https://wall.tg/blog/durov-wall-telegram-en","api_url":"https://wall.tg/api/v1/blog/durov-wall-telegram-en"},{"slug":"how-to-use-wall","lang":"en","title":"How to Use Wall — Complete Guide to the Social Platform in Telegram","url":"https://wall.tg/blog/how-to-use-wall","api_url":"https://wall.tg/api/v1/blog/how-to-use-wall"},{"slug":"wall-platform-story-en","lang":"en","title":"Durov Brought Back the Wall — Without Meaning To","url":"https://wall.tg/blog/wall-platform-story-en","api_url":"https://wall.tg/api/v1/blog/wall-platform-story-en"}]}