Email Risk Scorer
Pricing
$8.00 / 1,000 oa scrapeds
Email Risk Scorer
Score email addresses for fraud/spam risk: disposable domains, MX validation, role accounts, and an AI judgment layer for ambiguous cases. $0.004 per scored email.
Pricing
$8.00 / 1,000 oa scrapeds
Rating
0.0
(0)
Developer
AutomateLab
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Zalo OA Scraper — Public Zalo Official Account Data (OA Profiles, Verified Badge, QR)
Scrape public Zalo Official Account (OA) pages on zalo.me: OA ID, account name, verified flag, category, description, avatar, QR deep-link image, public address and working hours — as clean JSON, CSV or Excel.
No login. No QR session. No Zalo account. No Bright Data. You are charged only for public OA records actually delivered — login-walled, not-found and unreachable targets are always free.
Why this Zalo scraper
- Public data only, by design. Reads exactly the landing payload a logged-out browser sees. No chats, no contacts, no group rosters — out of scope and out of reach (Vietnam PDPL-friendly).
- First-party decode. Zalo server-renders OA pages inside an obfuscated payload; this actor decodes it directly over plain HTTPS — fast, cheap, no browser, no headless Chrome, no proxy required.
- CRM-enrichment ready. One stable record per OA: canonical
oaId, custom slug, verified checkmark, tier, category (vi/en), address, working hours, avatar + QR URLs. - Clear statuses. Every input row produces a row:
public,login_required,not_found, orerror. A login redirect is never misreported as a profile. - AI/agent ready. Call it from Apify MCP, n8n, Make, or any HTTP client.
Use cases
| Use case | What you get |
|---|---|
| Brand / OA directory building | Canonical OA ID, name, verified flag, category |
| Vietnam market research | Public OA descriptions, categories, tiers at scale |
| Store / branch data | Public address + working hours where the OA publishes them |
| QR / deep-link ops | QR image URL + message argv for the public OA |
| CRM enrichment | Structured OA rows from a list of zalo.me links |
Input
| Field | Type | Description |
|---|---|---|
startUrls | array | Public zalo.me/... OA URLs — numeric (https://zalo.me/4462152339089565647) or custom slugs (https://zalo.me/officialaccount) |
oaIds | array | Numeric Official Account IDs (10–24 digits) |
slugs | array | Custom OA slugs (the path after zalo.me/) |
maxItems | integer | Dataset cap (default 100) |
proxyConfiguration | object | Optional; public OA pages normally need no proxy |
Mix all channels freely — merged and de-duplicated by OA ID. Group invite
links (zalo.me/g/...) are not public on the web and are rejected.
Output (one record per public OA)
status · oaId · slug · canonicalUrl · name · description ·
avatarUrl · qrCodeUrl · isVerified · category · categoryEn ·
tier · type · address · workingHours · url
Cost — success-only billing
Pay-per-event: oa-scraped charged once per public OA record delivered.
| Outcome | Charged? |
|---|---|
| Public OA profile delivered | Yes — $0.008/record |
login_required (login wall) | Free |
not_found | Free |
error (network/upstream) | Free |
| Run summary record | Free |
FAQ
Is this the official Zalo Open API? No — it reads public OA landing pages, the same payload a logged-out browser sees. It is not affiliated with Zalo/VNG.
Does it read private chats or messages? Never. Private conversations, contacts and group rosters need a logged-in Zalo account and are hard out of scope.
Do I need a proxy? Usually not. Public OA landing pages fetch fine over plain HTTPS; enable Apify Proxy only for very large batches.
Example
