Telegram Channel Scraper — Python client
Collect posts and history from supplied public Telegram channels.
This client starts the hosted Apify Actor, waits for completion and downloads Dataset records. It also reads SUMMARY and ERRORS when available. Source coverage and result fields depend on the Actor.
Install
pip install apivault-telegram-public-channels-scraper
Run
Set APIFY_TOKEN in your environment. Replace the example values with your own valid inputs from the Actor input form.
from apivault_telegram_public_channels_scraper import Client, WaitTimeout
client = Client()
actor_input = {
"channels": [
"telegram"
],
"maxPostsPerChannel": 10,
"maxResults": 10
}
result = client.run(actor_input, max_total_charge_usd=0.05, max_rows=100)
print(result.run_id, len(result.rows), result.truncated)
print(result.summary)
An Apify account and token are required. The package has no subscription of its own; hosted runs are billed by Apify under the Actor pricing. The event charge cap may not include platform usage. Review the current price before changing it. max_rows limits the download, not the Actor collection or its charges; configure an Actor result limit too.
Resume and diagnostics
client.start(input) returns a run ID; client.wait(run_id) and client.result(run_id) resume an existing run. A WaitTimeout exposes run_id. Starting a run is never automatically retried. Use an existing run ID after a connection or waiting failure to avoid duplicate paid runs. Failed and aborted runs raise ActorError. No-match and partial results require inspecting summary and errors; diagnostic rows must not be mistaken for useful results.
Rows can be serialized as JSON or used in your own CSV/Excel pipeline. Native Dataset exports are available in Apify. Optional integrations and credentials depend on the Actor.
Hosted Actor В· Source В· PyPI
Related integration
Metadata
Release files for apivault-telegram-public-channels-scraper 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| apivault_telegram_public_channels_scraper-0.1.0.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apivault_telegram_public_channels_scraper-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / apivault_telegram_public_channels_scraper-0.1.0.tar.gz
| Download URL | apivault_telegram_public_channels_scraper-0.1.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f51a309df06123164c90ca2380ce91776cb0dae2db2ba246f6394f7be071004
|
|
BLAKE2b-256 checksum How to use checksums |
c8bc0144ff68d2cd5e033f84d29f5a4ef174179a1e6d969b97a806456b3b511f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / apivault_telegram_public_channels_scraper-0.1.0-py3-none-any.whl
| Download URL | apivault_telegram_public_channels_scraper-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a516c3276758596cd5367fb8729f286e8ac34718f708a779785ffb39df1362e
|
|
BLAKE2b-256 checksum How to use checksums |
914f1e66a9176799f5e23f8b01c5311d0f0ff74eef5fa28417b151007ae9968b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for apivault-telegram-public-channels-scraper 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.