Active user check
Return whether a phone number is likely connected to an active Telegram user.
Add Telegram user verification, bot-risk signals, and bulk list checks to your backend with one developer-friendly API.
bulkchecker.io helps product, growth, and risk teams verify phone-based Telegram lists before outreach, onboarding, airdrops, or enrichment workflows.
{
"telegram_user": true,
"active_status": "likely_active",
"bot_risk": "low"
}
Use one API to verify Telegram availability, enrich risk decisions, and process large lists without manual review.
Return whether a phone number is likely connected to an active Telegram user.
Submit up to 10K numbers per request and collect results through polling or webhooks.
Add risk bands for bot-like, duplicate, or low-trust patterns in Telegram-heavy workflows.
Receive async completion events for batch jobs, exports, and queue-based verification systems.
Create an API key, make your first request, and map the response fields into your product logic.
Create a bulkchecker.io workspace, generate a server-side key, and set project usage limits.
curl -X POST https://api.bulkchecker.io/v1/telegram/check \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone": "+14155550198",
"include_bot_risk": true
}'
{
"id": "tgc_8d92a1",
"phone": "+14155550198",
"telegram_user": true,
"active_status": "likely_active",
"bot_risk": "low",
"confidence": 0.96,
"message_sent": false,
"checked_at": "2026-05-10T09:30:00Z"
}
Use synchronous checks for product flows and async batch jobs for high-volume Telegram verification.
Use a native client library or call the REST API directly from your backend service.
Keep Telegram checks on your server, enrich records after validation, and avoid exposing keys in client-side code.
const result = await bulkchecker.telegram.check({
phone: "+14155550198",
includeBotRisk: true
});
Start with test credits, then move to volume tiers for automated Telegram checks and bulk jobs.
Build Telegram verification into the workflows where inactive, fake, or risky accounts create downstream cost.
Score Telegram-linked phone lists before airdrops, allowlists, quests, and token community campaigns.
Filter inactive contacts, enrich CRM records, and prioritize Telegram-ready leads before sales workflows.
Add Telegram availability and risk context to lawful research, compliance review, and investigative data hygiene.
Answers about limits, privacy, and bot-risk signals.