Open Measures Telegram channel post API pricing
Is Open Measures yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
50% complete: 2 of the 4 fields on our checklistSee the 4 fields
$0.00per 1,000 postsWe haven't run Open Measures through our Telegram channel post API benchmark yet.This plan is free. We rank 98 plans for Telegram channel post APIs by price. Half of the ranked plans cost $0.05 or less per 1,000 posts. 36 Telegram channel post API plans on our price sheet are free. ScrapeAtlas has a free plan with 100 pages of posts in total. ScrapeAtlas is the best Telegram channel post API in our benchmark.Zapi's Rp399,000 (about $22) monthly plan is the cheapest paid plan per 1,000 posts: $0.0011. Zapi charges for each page of results. We count 20 posts on each page to get the $0.0011 price. For 10,000 posts a month, SandBase's top-up plan costs the least: $0.10 a month.ScrapeAtlas, TrueScrape and Scrappa are the best Telegram channel post API providers in the Datacircle benchmark.
Plan: Public one of Open Measures' 3 plans
Call:
GET / content Open Measures' only callAPI: Telegram channel post API one of Open Measures' 4 APIs
- Open Measures Bluesky post API
- Open Measures Telegram channel post API
- Open Measures TikTok video API
- Open Measures Truth Social post API
About this item
- A copy at most 6 months old. You get posts from Open Measures' copy of Telegram.
- 2 of the 4 fields on our checklist. Text, Author.
- Nothing to pay. You get 39 requests a day. Each page uses one request. Calls stop once your requests run out.
- One call. You send
termtoGET /. You setcontent siteto "telegram". You can also sendquerytype,since,until,sortdescandlimit. The call returns the channel's posts. - Anyone can get it. Keep data: no API terms. Use data: no API terms.
Open Measures: Telegram channel post API alternatives
Open Measures alternatives: other Telegram channel post API providers by price
We list other providers' plans closest to this plan in price per 1,000 posts. Each plan in the table gives live data or data at most a year old.
| This planOpen Measures, free | TrueScrape, free | FetchGoblin, free | glim.sh, free | Scrape Everything, free | |
|---|---|---|---|---|---|
| $ per 1,000 posts | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Completeness | 50% | 100% | 100% | 100% | 75% |
| Billing | free | free | free | free | free |
| Pay | $0 | $0 | $0 | $0 | $0 |
| Enough for | 39 pages a day | 1,000 pages | 50 pages, once | 200 pages | 50 pages, once |
| Freshness | 6 months | live | live | live | live |
| Who can get it | anyone | anyone | anyone with a Google account or a permanent email address, who has authority to enter the terms for themselves or their organization | anyone who signs in at glim.sh/app with an email code: new accounts get $1 of free calls | one new account each: anyone 18 or over who can enter a binding contract |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-15.
- api.openmeasures.io/openapi.json
- docs.openmeasures.io/docs/further-reading/faq
- docs.openmeasures.io/docs/guides/public-api
- gitlab.com/openmeasures/backends/openmeasures-api/-/raw/main/smat_be/es_config.py
- openmeasures.io/api-advice
- openmeasures.io/new-feature-platform-and-pro-api-release
- openmeasures.io/platform
- openmeasures.io/update-to-public-api
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Text
- Media, not in the answer
- Engagement, not in the answer
- Author
| $ per 1,000 posts | $0.00 |
|---|---|
| Per | page of 10,000 |
| Billing | free |
| Aggregators | none |
|---|
| Also pays for | from the same budget: Timeseries · Activity |
|---|
| Units cap | hard |
|---|
| $ per 1,000 calls that find nothing | $0.00 |
|---|
| Their pitch | Return the content from a source. Use this to search for posts. |
|---|
| Freshness | 6 months |
|---|---|
| Keep data | no API terms |
| Use data | no API terms |
| Pay | $0 |
|---|---|
| You get | 39 requests a day |
| Enough for | 39 pages a day |
| Per day | 39 |
|---|---|
| Batch | 1 |
| Answer | in the call |
|---|
| You send | term, site "telegram". Optional: querytype, since, until, sortdesc, limit |
|---|---|
| Method | GET |
| Path | /content |
| Plan | Public |
|---|---|
| Who can get it | anyone |
The 6 fields the plan's answer can hold
username, channel name, text, view count, created at, author