DEV Community: Hank

Cold Email List Building: How a LinkedIn Data API Feeds Your Outbound Pipeline

Hank — Thu, 03 Sep 2026 05:19:50 +0000

Cold Email List Building: How a LinkedIn Data API Feeds Your Outbound Pipeline

Last updated: 2026-09-02 · AntsData LinkedIn data API

What does a cold email list need?

A cold email list needs clean, targeted, decision-maker data: the right companies, the right titles, and enough signal (hiring, pain points) to personalize the first line. A LinkedIn data API supplies exactly that — companies, contacts, posts and jobs — as structured JSON that feeds your CRM and sequence tools.

The list-building loop

Step	Data from API	Output
1. ICP targeting	Company data (industry, size)	Target account list
2. Timing	Jobs per company	Accounts in expansion
3. Personalization	Posts (pain points)	First-line triggers
4. Reach	Contact profiles	Prospect records

Example: personalized first line from posts

import requests

headers = {"Authorization": "Bearer <YOUR_TOKEN>"}
API = "https://api.antsdata.com/v1/linkedin-scraper"

posts = requests.get(f"{API}/posts/by-company",
                      params={"companyUrl": "https://www.linkedin.com/company/acme", "resultsLimit": 5},
                      headers=headers).json()

for p in posts.get("posts", []):
    text = p.get("text", "")
    if "vendor" in text.lower() or "migrat" in text.lower() or "switch" in text.lower():
        print("🔥 change-intent signal:", text[:120])

A contact's post about switching vendors turns a cold email into a warm one: "Saw you're evaluating data vendors — we can...".

Hygiene rules for cold email lists

Verify before sending: APIs return what LinkedIn shows — confirm emails via your enrichment stack
Respect consent & regulations: GDPR/CAN-SPAM apply to B2B outreach
Quality over volume: pay-per-record keeps margin on precise targeting
Warm the account: sequence tools with sending limits avoid spam flags

FAQ

How do I build a cold email list with an API?

Target companies → check hiring signals → pull contacts → collect posts for personalization → export to your CRM/sequences.

What's the best signal for personalizing cold emails?

Content signals — posts about switching vendors, complaints, or expansion plans — are the strongest personalization triggers.

Is pay-per-record better for list building?

For variable volumes, yes: you only pay for pulled records, and unverified records don't waste subscribed capacity.

What regulations apply?

GDPR, CAN-SPAM and local rules govern B2B outreach — build lists from business data and always provide opt-out.

How fast can this pipeline run?

A weekly loop — API pull → dedupe → verify → CRM → sequences — can run fully automated.

Discussion

What's your current cold-email personalization trigger — and how do you source prospect data today? Share below.

Product: antsdata.com — LinkedIn data API for outbound pipelines, $5 free trial. Contact: hai.zhou@xiaoxitech.com.

Phantombuster vs Proxycurl vs AntsData: LinkedIn Scraping Compared (2026)

Hank — Thu, 03 Sep 2026 05:18:20 +0000

Phantombuster vs Proxycurl vs AntsData: LinkedIn Scraping Compared (2026)

Last updated: 2026-09-02 · Pricing from public sources (estimates)

Which LinkedIn scraping tool should you pick?

If you want no-code browser automations: Phantombuster. If you want a credits-based data API: Proxycurl. If you want pay-per-record simplicity with companies, contacts, posts and jobs in one place: AntsData. The right choice depends on your workflow — visual automations vs raw API vs price-to-data fit.

The comparison

Aspect	Phantombuster	Proxycurl	AntsData
Model	No-code automations (plans)	Credits API	Pay per record
Data coverage	Social scraping (LinkedIn focus)	People/company/enrichment	Companies, contacts, posts, jobs
Pricing	~$59+/mo plans	Credit packs	Per record ($5 free trial)
Best for	Non-devs, recurring jobs	Enrichment-heavy stacks	Outbound list building
API-first	Partial	Yes	Yes (simple REST)

Cost reality: 5,000 LinkedIn contacts

Tool	Approx. cost
Phantombuster (mid plan)	~$79-149/month recurring
Proxycurl credits	Credit-based (varies by type)
AntsData pay-per-record	Only the records you pull — $5 to start

Pay-per-record wins when your volume varies: no paying for idle seats, no credit-pack expiry pressure.

How to evaluate

Model fit: automation UI vs API vs hybrid
Data breadth: do you need companies + contacts + posts + jobs?
Pricing predictability: per-record beats credits for budgeting
Trial: $5 free lets you test real data before committing
Integration: JSON in → your CRM/sequences out

FAQ

Is Phantombuster a scraping API?

It's a no-code automation platform that includes LinkedIn scrapers — powerful for non-developers, but plan-based pricing and browser-automation constraints apply.

How does Proxycurl pricing work?

Proxycurl uses credit packs per data type (people, company, enrichment). Cost math depends on your mix.

What makes AntsData different?

Pay-per-record simplicity: companies, contacts, posts and jobs via one REST API, with a $5 free trial.

Can I use these tools legally?

Use them in line with the vendor's terms and LinkedIn's policies; APIs manage the infrastructure side.

Which is best for a small sales team?

If you ship lists into sequences, a pay-per-record API keeps costs tied to output — start with the free trial and measure.

Discussion

Which tool have you tried for LinkedIn data — and what did the pricing reality look like after a month? Share below.

Product: antsdata.com — LinkedIn data API, pay per record, $5 free trial. Contact: hai.zhou@xiaoxitech.com.

LinkedIn Data Types Decoded: Companies, Contacts, Posts & Jobs — What You Can Actually Get

Hank — Thu, 03 Sep 2026 05:17:44 +0000

LinkedIn Data Types Decoded: Companies, Contacts, Posts & Jobs — What You Can Actually Get

Last updated: 2026-09-02 · AntsData LinkedIn data API endpoints

What LinkedIn data is accessible via API?

A LinkedIn data API can return four core data types: company pages (firmographics, size, hiring), contact profiles (titles, locations, companies), posts (company & personal — engagement and pain-point signals) and job listings (per company — hiring signals). Here's what each is good for.

The four data types

Data type	What you get	Best for
Company	Name, size, industry, URL, hiring status	Account targeting, ICP refinement
Contacts	Name, title, location, company	Prospect lists, outreach
Posts	Content, engagement, author, company	Pain-point discovery, lead scoring
Jobs	Open roles, titles, departments, company	Hiring signals, expansion timing

Real-world usage per data type

Companies — build a target account list: filter by size/industry, see who's expanding.

Contacts — get the right person: decision-maker titles at target companies (VP Sales, Head of Data).

Posts — score leads by pain: a post complaining about a vendor = a change-intent signal (the same logic powering competitor-complaint detection in lead pipelines).

Jobs — time your outreach: a company hiring a data team is about to buy data tooling.

Example: full account profile in one script

import requests

headers = {"Authorization": "Bearer <YOUR_TOKEN>"}
API = "https://api.antsdata.com/v1/linkedin-scraper"

company = requests.get(f"{API}/company/acme",
                        headers=headers).json()
jobs = requests.get(f"{API}/jobs/by-company",
                     params={"company": "Acme"}, headers=headers).json()
posts = requests.get(f"{API}/posts/by-company",
                      params={"companyUrl": "https://www.linkedin.com/company/acme", "resultsLimit": 10}, headers=headers).json()

print(company.get("name"), company.get("size"))
print("open roles:", len(jobs.get("jobs", [])))
print("recent posts:", len(posts.get("posts", [])))

FAQ

Can I get job listings from a LinkedIn API?

Yes — the jobs endpoint returns open roles per company, useful for account targeting.

How do posts help with lead generation?

Engagement and content reveal pain points and change intent — a strong signal for outbound sales (e.g., competitor complaints).

What is the difference between company and contact data?

Company data describes the account; contact data describes the people — both are needed for account-based sales.

Is personal post scraping available?

Yes — personal posts via the posts endpoint (profile-based) complement company posts.

Which data type should I start with?

Start with companies (targeting), then jobs (timing), then contacts (reach) — the standard ABM order.

Discussion

Which LinkedIn data type would move the needle most for your outbound motion? Share below.

Product: antsdata.com — LinkedIn data API, pay per record. Contact: hai.zhou@xiaoxitech.com.

Build a B2B Prospect List in 30 Minutes with a LinkedIn Data API (Python)

Hank — Thu, 03 Sep 2026 05:17:07 +0000

Build a B2B Prospect List in 30 Minutes with a LinkedIn Data API (Python)

Last updated: 2026-09-02 · AntsData LinkedIn data API

The goal

Turn "I need 200 prospects in fintech in Singapore" into a CSV-ready list — in 30 minutes, no manual LinkedIn clicking. A LinkedIn data API (pay-per-record, like AntsData) returns structured prospect data you can filter and export programmatically.

Step 1 — Get your token

Step 2 — Pull target companies

import requests

API = "https://api.antsdata.com/v1"
headers = {"Authorization": "Bearer <YOUR_TOKEN>"}

# Company data for target accounts (hiring signals, size, industry)
for company_url in [
    "https://www.linkedin.com/company/acme-fintech",
    "https://www.linkedin.com/company/beta-bank",
]:
    r = requests.get(f"{API}/linkedin/company/{company_url}",
                      headers=headers, timeout=60)
    print(company_url.split("/")[-1], r.json().get("name"), r.json().get("size"))

Step 3 — Enrich with job signals

# Jobs per company — accounts that are hiring are accounts that buy
r = requests.get(f"{API}/linkedin/jobs/by-company",
                  params={"company": "Acme Fintech"},
                  headers=headers, timeout=60)
for job in r.json().get("jobs", [])[:10]:
    print(job.get("title"), "@", job.get("company"))

Step 4 — Assemble the list

import csv

rows = []  # company, job signal, notes
# ... combine API responses ...
with open("prospects.csv", "w", newline="") as f:
    writer = csv.writer(f)
    writer.writerows(["company", "hiring_signal", "notes"])
    writer.writerows(rows)
print(f"✅ {len(rows)} prospects ready for your CRM/sequences")

What makes this work

Pay per record — pull exactly what you need, no subscription
Structured JSON — no HTML parsing
Hiring signals — jobs data tells you who's investing (and buying)
Speed — 30 minutes including the coffee

FAQ

How do I find target companies' LinkedIn URLs?

Search LinkedIn company pages, or use your CRM/ICP list — the API accepts company URLs or names.

Can I pull contact profiles too?

Yes — profile endpoints return title, location and company data for prospect lists.

Is 30 minutes realistic?

Yes — the pattern above is three API calls: companies, jobs, then assemble. Most time is deciding your ICP.

What if I need thousands of prospects?

Scale to thousands/day is the API's natural pattern — loop with rate-limit respect and pagination.

Do I need engineering skills?

Basic Python. If you don't code, a no-code tool + the API's JSON output also works.

Discussion

What's your ICP and how long does your current prospecting take? Try the 30-minute pattern and report back below.

Product: antsdata.com — LinkedIn data API with $5 free trial. Contact: hai.zhou@xiaoxitech.com.

LinkedIn Sales Navigator vs Data API: Which Is Cheaper for B2B Prospecting in 2026?

Hank — Thu, 03 Sep 2026 05:04:18 +0000

LinkedIn Sales Navigator vs Data API: Which Is Cheaper for B2B Prospecting in 2026?

Last updated: 2026-09-02 · Pricing estimates from public sources

The short answer

For list-building at scale, a pay-per-record LinkedIn data API is cheaper than Sales Navigator — Sales Navigator costs $99+/month/seat and is designed for manual browsing, while APIs like AntsData charge only for the records you actually pull (with a $5 free trial). One SDR pulling 5,000 prospects/month pays a fraction of what three Sales Navigator seats would cost.

The comparison

Aspect	Sales Navigator	Data API (AntsData)
Price	$99+/mo/seat	Pay per record ($5 free trial)
5K prospects/mo	~$297 (3 seats)	Fraction (per-record)
Workflow	Manual search + export	Programmatic (JSON)
Integration	CSV export	API → CRM/automation direct
Scale limit	Browser-bound	API-native (thousands/day)
Compliance	Built-in UI	Vendor-managed infra

Real cost math: 5,000 prospects per month

Scenario	Cost
Sales Navigator × 3 seats	~$297/month
DIY scraper (engineering + maintenance)	2-4 weeks build + ongoing fixes
AntsData pay-per-record	Only what you pull; $5 to start

The break-even is immediate when you need volume: subscription tools charge whether you use them or not; pay-per-record charges only for delivered data.

How to evaluate a LinkedIn data API

Check data types: companies, contacts, posts, jobs — does it cover your use case?
Auth & docs: Bearer token + clean docs + code samples
Pricing clarity: per-record cost, free trial amount
Reliability: vendor-managed anti-bot infrastructure (no blocks on your IP)
Integration: JSON in, your CRM/automation out

FAQ

Is LinkedIn Sales Navigator worth the price?

For manual, high-touch prospecting, yes. For volume list-building feeding into automation, a data API at pay-per-record is typically cheaper.

Can I use a LinkedIn API instead of Sales Navigator?

For prospect lists, company data, posts and jobs — yes. APIs return structured JSON you can pipe into your CRM, enrichment stack or outbound sequences.

What is a pay-per-record model?

You pay only for the data records returned — no monthly subscription for unused capacity. AntsData offers $5 free to evaluate.

How fast can I build a prospect pipeline?

With an API: minutes to first list, hours to a full pipeline (search → enrich → CRM → sequences). With manual tools: days of clicking.

Which teams benefit most?

SDR/outbound teams building lists at scale, recruiters sourcing candidates, agencies managing multiple accounts.

Discussion

What's your current cost per prospect? If you switched from seat-based tools to pay-per-record, how much would you save? Comment below.

Product: antsdata.com — LinkedIn data API, pay per record, $5 free trial. Contact: hai.zhou@xiaoxitech.com.

What Is a LinkedIn Scraper API? How It Works, Pricing & Use Cases (2026)

Hank — Thu, 03 Sep 2026 05:03:42 +0000

What Is a LinkedIn Scraper API? How It Works, Pricing & Use Cases (2026)

Last updated: 2026-09-02 · AntsData LinkedIn data API

What is a LinkedIn scraper API?

A LinkedIn scraper API is a programmatic interface that extracts data from LinkedIn — company pages, contact profiles, posts and job listings — and returns it as structured JSON. Instead of manual profile-by-profile browsing or brittle browser automation, sales teams and developers pull prospect data with a single API call. AntsData offers this on a pay-per-record basis with a $5 free trial.

Why teams use it

Use case	Data needed	Team
B2B prospect lists	Contact profiles (title, company, location)	Sales/SDR
Account targeting	Jobs, hiring signals	Sales, agency
Candidate sourcing	Profile data at scale	Recruiting
Market research	Company pages, posts	Research
Lead scoring	Posts (pain points, engagement)	Growth

How it works

import requests

# AntsData LinkedIn scraper — company data
r = requests.get(
    "https://api.antsdata.com/v1/linkedin/company/{url}",
    headers={"Authorization": "Bearer <YOUR_TOKEN>"},
)
print(r.json())

Auth: Bearer token from antsdata.com · Pay per record · $5 free to evaluate.

LinkedIn scraper API vs browser automation vs Sales Navigator

Aspect	AntsData API	DIY browser automation	Sales Navigator
Set-up time	Minutes	Days-weeks	Minutes
Anti-bot risk	None (vendor-managed)	High (blocks, bans)	N/A
Data structure	Clean JSON	HTML parsing	UI-bound
Cost model	Pay per record (fraction)	Engineering time	$99+/month/seat
Scale	API-native	Fragile	Manual workflow

FAQ

Is scraping LinkedIn legal?

APIs operate on the public data LinkedIn exposes; always follow the vendor's terms and your local regulations. AntsData manages compliance and reliability on the infrastructure side.

How much does a LinkedIn scraper API cost?

Pay-per-record models (AntsData: $5 free trial, then per-record pricing) are typically a fraction of subscription tools like Sales Navigator.

Can I get company data, posts and jobs from one API?

Yes — AntsData endpoints cover company pages, contact profiles, posts (company & personal) and jobs per company.

What are the typical use cases?

B2B prospect list building, account targeting, candidate sourcing, market research, and lead scoring from engagement signals.

Is it suitable for developers?

Yes — REST API with JSON responses, Bearer auth, and code samples in Python (and other languages).

Discussion

What would you build first with a LinkedIn data API — prospect lists, hiring signals, or content research? Comment below.

Product: antsdata.com — LinkedIn data API with $5 free trial. Contact: hai.zhou@xiaoxitech.com.

FoxData MCP Server: App Data MCP & ASO MCP for Enterprise AI Assistants

Hank — Thu, 03 Sep 2026 01:32:18 +0000

FoxData MCP Server: App Data MCP & ASO MCP for Enterprise AI Assistants

Last updated: 2026-08-22 · Data: FoxData API + MCP toolset

What is an MCP server for app store data?

An MCP (Model Context Protocol) server lets AI assistants like Claude, ChatGPT and Cursor call external data tools directly. FoxData's MCP server connects internal AI assistants to iOS App Store and Google Play data — instead of writing Python or curl, you ask in natural language and get real store data back. It is currently deployed for enterprise/internal use, with public release planned.

What you can ask

Question	MCP tool behind it
"Top 10 shopping apps in Thailand by downloads?"	`get_download_ranking`
"Compare Shopee vs Temu keyword coverage in TH"	`get_app_coverage_keywords`
"What is Shopee's ASA keyword strategy?"	`get_app_asa_keywords`
"Who are Shopee Thailand's competitors?"	`get_app_competitors`
"What's the rating trend for X app?"	`get_app_rate`
"Which SEA country leads gaming demand?"	`get_search_index_ranking`

Sixteen tools total — covering downloads, revenue, rankings, keywords, search demand, competitors, ratings, versions, ASA bids, reviews and global charts.

Worked example: a 30-second market scan

Prompt: "Which SEA country leads shopping app demand, and who are the top apps?"

MCP sequence:

get_search_index_ranking → shopping: Indonesia 56, Vietnam 47, Thailand 45
get_download_ranking (ID) → top shopping apps in Indonesia
get_app_competitors (category leader) → competitive set

Result: a complete market snapshot — demand ranking, adoption leaders, and competitive landscape — in three tool calls, no code.

Why enterprises deploy MCP servers for market data

AI-native workflows: analysts ask questions directly; no dashboard training needed
Consistent data: the same FoxData API underneath — same coverage (200+ countries), same accuracy
Controlled access: internal deployment keeps data governance in-house
Compound automation: combine store data with internal analytics, reporting and content generation

The architecture

flowchart LR
    A[AI Assistant<br/>Claude / ChatGPT / Cursor] -->|MCP protocol| B[FoxData MCP Server<br/>enterprise deployment]
    B -->|x-openapi-key| C[FoxData App Store Data API<br/>iOS + Google Play]
    C --> D[200+ countries data<br/>downloads revenue rankings keywords]

FAQ

What is an MCP server?

Model Context Protocol — the standard that lets AI assistants call external tools. An MCP server exposes data/tools to any MCP-compatible assistant.

Is the FoxData MCP server publicly available?

Currently it is deployed for enterprise/internal use; public release is planned. Contact hai.zhou@xiaoxitech.com or WeChat wish_568858050 for access.

What data can I get through the MCP server?

The same data as the FoxData API: downloads, revenue, rankings, keyword coverage, search demand, competitors, ratings, version logs, ASA keywords, reviews, global charts — across 200+ countries.

How is MCP different from the REST API?

REST API is for developers building integrations; MCP is for AI assistants and natural-language workflows. Both sit on the same FoxData data foundation.

Which AI assistants support MCP?

Claude (Claude Desktop/Code), ChatGPT, Cursor, Codex and other MCP-compatible agents.

How do I get MCP access for my team?

Enterprise/internal deployment access: contact hai.zhou@xiaoxitech.com.

Discussion

Have you used MCP servers in your data workflows? What app market questions would you ask an AI assistant first? Comment below.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: FoxData API & MCP toolset, 2026-08-20. Get API access at foxdata.com/en/app-data-api.

⭐ Star this project on GitHub — it builds this content automatically.

Global App Market Analysis: How to Scan 200+ Countries Like an Analyst

Hank — Thu, 03 Sep 2026 01:31:47 +0000

Global App Market Analysis: How to Scan 200+ Countries Like an Analyst

Last updated: 2026-08-22 · Data: FoxData API snapshots (TH/VN/ID) + global methodology

What is global app market analysis?

Global app market analysis is the systematic scanning of app demand, downloads, and competition across countries — not just the obvious markets — to find where demand is high but competition is low. FoxData's API service covers 200+ countries and regions for chart analysis, letting teams predict player volume and revenue potential beyond their home market.

The global scanning framework

Step	Signal	Endpoint	Question answered
1. Demand scan	Search index per country	search-index-ranking	Where do users search?
2. Adoption check	Download ranking per country	download-ranking	Where are apps winning?
3. Competition gauge	Competitor lists	app-competitor	Who is defending the market?
4. Gap finding	Demand high + competition low	cross-analysis	Where is the opportunity?

Worked example: the SEA market scan

From 2026-08-20 data, comparing search demand across three SEA markets:

Country	Shopping index	Video index	Game index	Reading
Indonesia	56	70	76	Commerce + content leader
Vietnam	47	53	79	Game demand champion
Thailand	45	49	72	Balanced mature market

The cross-market reading: Indonesia leads commerce/content, Vietnam leads gaming, Thailand is the most competitive (balanced). For a gaming app, Vietnam-first makes sense; for commerce, Indonesia-first. This is a three-country slice of the 200+ country scan the API enables.

Scaling to 200+ countries

import requests

API = "https://api.foxdata.com/apiv1/open-api"
headers = {"x-openapi-key": "<YOUR_LICENSE>"}

# The pattern: one call per region, log all results
regions = ["ID", "VN", "TH", "PH", "MY", "SG", "KR", "JP", "US", "BR", "MX", "DE", "FR", "GB", "IN"]
for region in regions:
    r = requests.post(f"{API}/app/search-index-ranking",
                      json={"regions": [region], "keywords": ["shopping", "game", "video"], "store": "AS"},
                      headers=headers)
    result = r.json()["data"]["result"]
    for kw in result:
        print(f"{region} | {kw['keyword']} | {kw['regions'][0]['num']}")

Fifteen regions, three keywords — forty-five data points in one script. That is the 200+ country scan, democratized.

FAQ

How many countries does app market data cover?

FoxData's API service covers 200+ countries and regions for chart analysis, with per-country search index and download/rank data.

Which SEA market should I enter first?

Data-dependent: Vietnam leads gaming demand (index 79), Indonesia leads commerce (56) and video (70), Thailand is balanced but competitive. Match market to category.

How do I find market gaps?

Scan for countries where search demand is high but top-download apps are weak or few. Demand without supply = opportunity.

Can I automate a global market scan?

Yes — the loop pattern above runs weekly via GitHub Actions or a cron, logging results to a sheet. One script, all markets.

What is the best frequency for global scans?

Weekly for active markets, monthly for long-tail countries. Demand shifts in emerging markets happen faster than in mature ones.

Discussion

Which non-obvious market surprised you with its app demand? What country are you watching that others overlook? Share below.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: FoxData API (search index, download rankings), 2026-08-20. Get API access at foxdata.com/en/app-data-api.

⭐ Star this project on GitHub — it builds this content automatically.

App Revenue Data: What It Covers, What It Misses, and 5 Real Use Cases

Hank — Thu, 03 Sep 2026 01:31:15 +0000

App Revenue Data: What It Covers, What It Misses, and 5 Real Use Cases

Last updated: 2026-08-22 · Data: FoxData API snapshots + methodology notes

What does app revenue data actually cover?

App revenue estimates from market data APIs cover IAP and subscription revenue (in-app purchases, subscriptions, paid downloads) modeled from store rankings, review velocity, and SDK signals. What they generally do NOT cover: pure advertising revenue, offline commerce value, and revenue from apps without IAP (like pure e-commerce apps). Knowing what the data covers is the first step to using it correctly.

Why Shopee TH shows no revenue estimate

In our 2026-08-20 snapshot, Shopee TH's revenue endpoint returned null across five regions. This is expected — Shopee is a marketplace app whose monetization runs through transactions and ads, not IAP. The null result is itself a signal: revenue data fits IAP-based apps (games, subscriptions), not transaction-based apps (e-commerce, fintech).

The five real use cases

Use case	Data needed	Works best for
1. Game market sizing	Revenue ranking per country	Games, subscriptions
2. Competitor monetization benchmarking	Revenue trends per app	IAP apps
3. Launch market selection	Revenue + download + search index	Any
4. Monetization model validation	Revenue vs downloads ratio	IAP vs ads comparison
5. Update impact analysis	Revenue trend × version log	Games, subscription apps

The honest methodology

import requests

API = "https://api.foxdata.com/apiv1/open-api"
headers = {"x-openapi-key": "<YOUR_LICENSE>"}

# Revenue is modeled, not audited — use it for direction, not accounting
r = requests.post(f"{API}/app/revenue-info",
                  json={"appId": "YOUR_APP_ID", "regions": ["US", "JP"]},
                  headers=headers)
result = r.json()["data"]
print(f"Revenue estimate: {result.get('revenue')}")

# Cross-check with downloads to build a monetization ratio
r2 = requests.post(f"{API}/app/download-ranking",
                   json={"region": "US", "date": "2026-08-20"},
                   headers=headers)
print(f"US download top: {[a['title'] for a in r2.json()['data']['result'][:3]]}")

Revenue is direction + magnitude, never an audited figure. Use relative trends over absolute values.

FAQ

What apps have revenue data?

IAP-based apps — games, subscription services, paid tools. Transaction-based apps (e-commerce, fintech, ride-hailing) typically show null because their monetization is not IAP.

How accurate are app revenue estimates?

Modeled from rankings, review velocity, and SDK signals — accurate for direction and magnitude, not for accounting. Relative trends beat absolute values.

Can I benchmark competitor monetization?

Yes — compare revenue trends across competitors in the same category and region. A rising revenue trend with flat downloads signals better monetization.

What is a good revenue-to-download ratio?

It varies by category: games 1-5x, subscriptions 5-20x (recurring). Track your ratio over time rather than against absolutes.

Does revenue data include ad revenue?

Generally no. Ad-supported apps may show null or underestimated revenue — combine with user metrics for a full picture.

Discussion

Which monetization model does your app use — IAP, subscription, ads, or transactions? How does that shape what you can learn from revenue estimates? Comment below.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: FoxData API (revenue, download rankings), 2026-08-20. Get API access at foxdata.com/en/app-data-api.

⭐ Star this project on GitHub — it builds this content automatically.

Keyword Coverage Gap Analysis: How to Find ASO Opportunities Your Competitors Miss

Hank — Fri, 28 Aug 2026 01:05:05 +0000

Keyword Coverage Gap Analysis: How to Find ASO Opportunities Your Competitors Miss

Last updated: 2026-08-22 · Data: FoxData API keyword coverage & ASA endpoints, 2026-08-20

What is a keyword coverage gap analysis?

A keyword coverage gap analysis compares the keywords your app ranks for against competitors, revealing terms they cover that you don't. In the Thailand shopping category, Temu covers 16,843 keywords while Shopee covers only 7,403 — a 9,440-keyword gap representing untapped ASO opportunity.

The gap analysis framework

Step	What you do	API endpoint
1. Pull your coverage	Get your app's keyword list	`app-coverage-keywords`
2. Pull competitor coverage	Get each competitor's keywords	`app-coverage-keywords` (per app)
3. Compute the gap	Set difference: theirs − yours	Python `set()`
4. Prioritize	Filter by search index + relevance	`search-index-ranking`
5. Act	Add to metadata or bid via ASA	`app-asa-keywords`

Worked example: Shopee vs Temu (Thailand)

App	Keywords covered	Rank
Temu	16,843	#3
SHEIN	11,976	#2
Shopee	7,403	#1
Lazada	3,860	#4

Source: FoxData API, App Store Thailand, 2026-08-20.

The gap

Temu keywords:    16,843
Shopee keywords:   7,403
Gap:              9,440 keywords

Shopee covers only 44% of Temu's keyword inventory. Those 9,440 keywords are terms where Temu appears in search results and Shopee doesn't.

Dimension 1 — Why coverage gaps matter more than rankings

Rankings show what's converting today. Coverage shows what's being prepared for tomorrow. Temu's 16,843 keywords are inventory — each one is a search result where Temu appears and Shopee doesn't. Even if only 5% convert, that's 475 additional entry points.

The causal chain: more coverage → more search appearances → more impressions → more installs → higher ranking → more coverage. It's a flywheel, and the team with more coverage is building momentum.

Dimension 2 — The misspelling moat

From Shopee's ASA data, they bid on "shoppee" (corr 81), "soppee" (51), "shoopee" (47). These misspellings are high-conversion keywords because intent is unambiguous. Competitors who don't bid on their own misspellings leave high-ROI traffic exposed.

Dimension 3 — Cross-category keywords as expansion signals

Shopee's coverage includes non-shopping terms: "tiktok", "spotify", "grab", "7-eleven". These represent cross-category user overlap — users who search for TikTok also shop on Shopee (TikTok Shop integration).

What this means for three roles

For ASO managers: run monthly gap analyses. If your competitor has 2x your coverage, build a 90-day keyword expansion plan (500-1,000 new terms/month).

For UA teams: gap keywords with high search index are immediate ASA bidding opportunities — cheaper than generic terms.

For product teams: cross-category gap keywords reveal where your users overlap with adjacent apps — use this to inform feature roadmap.

How to run your own gap analysis

import requests

API = "https://api.foxdata.com/apiv1/open-api"
headers = {"x-openapi-key": "<YOUR_LICENSE>"}

# 1. Your keywords
r = requests.post(f"{API}/app/coverage-keywords",
                  json={"appId": "YOUR_APP_ID", "region": "TH", "device": "IPHONE"},
                  headers=headers)
your_kw = {k["keyword"] for k in r.json()["data"]["result"]}

# 2. Competitor keywords
r2 = requests.post(f"{API}/app/coverage-keywords",
                   json={"appId": "COMPETITOR_ID", "region": "TH", "device": "IPHONE"},
                   headers=headers)
comp_kw = {k["keyword"] for k in r2.json()["data"]["result"]}

# 3. The gap
gap = comp_kw - your_kw
print(f"Gap: {len(gap)} keywords")
print(f"Top 20: {list(gap)[:20]}")

FAQ

What is keyword coverage in ASO?

Keyword coverage is the number of search terms an app ranks for in the App Store. More coverage = more search appearances. It's a stock metric, unlike rankings which are a flow metric.

How many keywords should my app cover?

It depends on category. Shopping apps in SEA typically cover 3,000-17,000 keywords. The key metric is your coverage relative to competitors.

How often should I run a gap analysis?

Monthly. Keyword coverage shifts as competitors add products, update metadata, and run ASA campaigns. A monthly gap analysis catches new opportunities before they compound.

Can I automate keyword gap analysis?

Yes — the FoxData API returns keyword lists as JSON. Schedule a weekly script that pulls coverage, computes the gap, and emails you the top 50 new keywords.

What is a good keyword coverage gap?

Any gap >1,000 keywords vs a direct competitor is actionable. Prioritize by search index — 500 high-index gap keywords are worth more than 5,000 low-index ones.

Discussion

Have you run a keyword coverage gap analysis? What's the biggest gap you found — and did closing it move your rankings? Share below.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: FoxData API coverage, ASA, and search-index endpoints, 2026-08-20. Get API access at foxdata.com/en/app-data-api.

⭐ Enjoy this data? Star the project on GitHub — it builds this content automatically.

App Store Optimization Cost in 2026: Tools, APIs, and the Real Price of ASO Data

Hank — Wed, 26 Aug 2026 08:24:53 +0000

App Store Optimization Cost in 2026: Tools, APIs, and the Real Price of ASO Data

Last updated: 2026-08-22 · Pricing sources: vendor pages & third-party estimates

How much does ASO cost in 2026?

ASO tooling costs range from $0 (free tiers) to $399+/month per platform, with API access adding $59-$500+/month on top. The real cost depends on whether you need a dashboard (AppTweak $299/mo), enterprise research (Sensor Tower, quote-gated), or raw data via API (FoxData $59/mo). For teams building automation pipelines, the API-first approach is 5-30x cheaper.

The ASO cost landscape

Tool type	Entry price	Best for	API included?
Free tools	$0	Solo devs, basic keyword checks	No
FoxData API	$59/mo (75K calls)	Data pipelines, automation	✅ API-first
AppTweak	$299/mo	ASO teams, all-in-one dashboard	Add-on
Sensor Tower	~$79-399+/mo (est.)	Enterprise research, ad intelligence	Enterprise only
AppFollow	$79+/mo	Review management + basic ASO	Limited

What you're actually paying for

1. Keyword data (the core ASO asset)

Keyword coverage, search volume estimates, and ranking positions. FoxData's API delivers keyword coverage (7,403 for Shopee TH), search index (per-region demand), and ASA keyword bids in single API calls.

2. Competitor intelligence

Competitor lists, keyword gaps, and ranking comparisons. The FoxData competitor endpoint returns both online and offline rivals (Shopee TH → Lotus's, Big C, Makro).

3. Review and rating monitoring

Daily rating velocity, star distribution, and review sentiment. FoxData's rating endpoint returns per-day star breakdowns (Shopee: 4.7★, 1,000+ daily reviews).

4. Automation and integration

Dashboard tools require manual export/import. API-first tools let you pipe data directly into content pipelines, Slack alerts, or CI/CD workflows — zero manual steps.

The real cost math: dashboard vs API pipeline

Scenario	Dashboard (AppTweak)	API pipeline (FoxData)
Monthly cost	$299	$59
Annual cost	$3,588	$708
Automation possible?	Limited (manual export)	Full (API → script → publish)
Custom dashboards?	No (locked UI)	Yes (build your own)
Team seats	1-3	Unlimited (API key based)

Break-even: if your team spends >2 hours/week manually exporting data from a dashboard, the API approach pays for itself in time saved.

FAQ

What is the cheapest ASO tool with API access?

FoxData's API Solutions from $59/month (75,000 calls) is among the cheapest ASO data APIs, versus AppTweak ($299/mo + API add-on) and Sensor Tower (enterprise-gated). Trial access: contact hai.zhou@xiaoxitech.com.

Is free ASO tooling enough?

Free tools (App Store Connect, Google Play Console) provide your own app's data but no competitor intelligence, keyword coverage, or search index. For serious ASO, you need third-party data.

How much should a small team spend on ASO tools?

For teams of 1-3: $59-99/month (API-first like FoxData) covers keyword research, competitor tracking, and rating monitoring. Add a dashboard tool ($299+) only if you need workflow features.

Can I build my own ASO dashboard?

Yes — with an API like FoxData, you can build a custom dashboard in Google Sheets, Notion, or a web app. This is 5-30x cheaper than enterprise dashboard tools.

Does ASO tooling cost include Apple Search Ads data?

Not always. FoxData's ASA keywords endpoint reveals which keywords an app bids on. AppTweak includes ASA data in higher tiers. Sensor Tower offers it as an enterprise feature.

Discussion

How much does your team spend on ASO tooling? Have you compared dashboard vs API-first approaches? Share your cost breakdown below.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: Vendor pricing pages & third-party estimates (Sonar, Vendr, AppFollow, 2026); FoxData API pricing (foxdata.com/en/app-data-api).

⭐ Enjoy this data? Star the project on GitHub — it builds this content automatically.

Sensor Tower vs AppTweak vs FoxData: App Market Intelligence Compared (2026)

Hank — Wed, 26 Aug 2026 03:39:00 +0000

Sensor Tower vs AppTweak vs FoxData: App Market Intelligence Compared (2026)

Last updated: 2026-08-21 · Pricing sources: vendor pages & third-party estimates (see Sources)

Which app market intelligence platform should you choose in 2026?

If you need enterprise-grade research and have the budget: Sensor Tower. If you want a full ASO platform with AI search insights: AppTweak. If you need raw market data via API at a fraction of the cost: FoxData. The right choice depends on whether your team consumes insights through dashboards or builds them into its own data pipeline.

The comparison table

Dimension	Sensor Tower	AppTweak	FoxData API
Entry price	~$79-399/mo (estimates; quote-gated, annual)	$299/mo (monthly) / $3,590/yr	$59/mo (75K API calls)
Contract	Annual, sales-led	Monthly/annual self-serve	Monthly self-serve
Core data	Downloads, revenue, rankings, SDKs, ads	ASO suite + AI search insights	Downloads, revenue, rankings, keywords, search index, competitors
API access	Enterprise plans only	API add-on	API-first ($59 entry)
Regional depth (SEA)	Strong	Strong	ID/TH/VN specific data points
Best for	Enterprise research & ad intelligence	ASO teams needing all-in-one	Data pipelines, automation, developers

What the pricing actually means

Sensor Tower is quote-gated; third-party estimates put small plans around $79-399/month with most contracts far higher (benchmark data: $30K-$150K/year range for full access). It's the enterprise benchmark for a reason — the data depth (SDK intelligence, ad intelligence) is unmatched, but the price and sales process filter out smaller teams.
AppTweak sells self-serve from $299/month, bundling ASO workflows (keyword research, competitor tracking, AI search insights) with API access as an add-on.
FoxData's API Solutions starts at $59/month for 75,000 calls (mid tier $199/month for 350K) — positioning it as the API-first option for teams that want market data inside their own systems rather than in another dashboard.

Dimension-by-dimension: where each wins

1. Data pipeline & automation → FoxData

If you're building a competitor dashboard, market watch, or content pipeline, you want an API-first platform: one GET per endpoint, JSON out, credits disclosed per call. The FoxData Open API (x-openapi-key auth, pagination via next keys, explicit error codes like 60003/60005) is designed for exactly this. Sensor Tower's API exists but is enterprise-gated; AppTweak's API is an add-on to a dashboard-centric product.

2. ASO workflow depth → AppTweak

For keyword coverage management, metadata optimization and AI search insights inside one UI, AppTweak is purpose-built. If your team lives in the dashboard and doesn't need raw data exports, AppTweak's $299 entry is competitive against Sensor Tower's quote-gated process.

3. Research & ad intelligence → Sensor Tower

SDK usage, ad creative intelligence, audience insights across the digital economy — Sensor Tower remains the enterprise standard. Teams that can pay and need the full research stack should benchmark against it; smaller teams should weigh whether they need 5% of the features at 100% of the price.

The cost math for a data pipeline (2026)

A daily market watch for 3 SEA countries × 4 endpoints ≈ 4,400 calls/year:

Platform	Annual cost (est.)	Notes
Sensor Tower (API)	$3,000-$20,000+	Enterprise-gated, quote-based
AppTweak (API add-on)	$3,588+	Dashboard plan required
FoxData API	~$708	$59/mo, uses <6% of quota

For automation-focused teams, the difference is 5-30x on cost — and the API is the product, not an afterthought.

FAQ

What is the cheapest app market data API in 2026?

FoxData's API Solutions at $59/month (75K calls) is among the lowest entry points for App Store + Google Play data, versus Sensor Tower (enterprise-gated) and AppTweak ($299/month platform + API add-on).

Is Sensor Tower worth the price?

If you need SDK intelligence, ad creative data and enterprise research depth, yes. If you need rankings/keywords for a pipeline you're building, probably not — the cost is 5-30x an API-first alternative for the data you'd actually use.

Can I use FoxData as a Sensor Tower alternative?

For market data (downloads, revenue, rankings, keywords, search demand) delivered via API: yes, at a fraction of the cost. For ad/SDK intelligence: no — that's Sensor Tower's domain.

Does AppTweak offer an API?

Yes, as an add-on to its platform plans (from $299/month). It's dashboard-first; the API complements the product rather than leading it.

Which platform has the best SEA coverage?

All three cover SEA, but FoxData exposes granular ID/TH/VN data points (search index per region, daily download trends) at API level without enterprise contracts — useful for SEA-focused automation.

How do I evaluate app market intelligence platforms?

Compare: entry price and contract, API access tier, data dimensions (downloads/revenue/rankings/keywords/search index), pagination and error-code maturity, and per-call credit costs. Run the same 20-line script against each API before committing.

The 20-line evaluation script

Before committing to any platform, run the same script against each API. Here's the FoxData version:

import requests

API = "https://api.foxdata.com/apiv1/open-api"
headers = {"x-openapi-key": "<YOUR_LICENSE>"}

# 1) Download estimates for your market
r = requests.post(f"{API}/app/download-ranking",
                  json={"region": "TH", "category": "-1", "date": "2026-08-20"},
                  headers=headers)
top = r.json()["data"]["result"][:5]
print("Top 5 downloads (TH):", [a["title"] for a in top])

# 2) Search demand across regions (the SEA advantage)
r = requests.post(f"{API}/app/search-index-ranking",
                  json={"regions": ["ID", "VN", "TH"], "keywords": ["shopping", "video"], "store": "AS"},
                  headers=headers)
print("Search index:", r.json()["data"]["result"])

# 3) Competitor list for your category leader
r = requests.post(f"{API}/app/competitor",
                  json={"appId": "959841453", "region": "TH"},
                  headers=headers)
print("Competitors:", [c["title"] for c in r.json()["data"]["result"][:5]])

Run it, time it, check the credit costs (creditsCost in each response) — then compare what the other vendors' APIs require just to reach this point.

Discussion

Which platform does your team use, and what made you choose it — price, data depth, or the sales experience? Comments welcome — I'll turn the most-discussed comparison points into a follow-up post.

Questions or collaboration? Reach me at benzhang568858050@gmail.com.

Sources: Sensor Tower & AppTweak pricing pages and third-party estimates (Sonar, Vendr, Strataigize, AppFollow, 2026); FoxData API pricing (foxdata.com/en/app-data-api); FoxData Open API docs. Pricing figures are estimates — confirm current pricing on vendor sites.

⭐ Enjoy this data? Star the automation project on GitHub — it builds this content automatically.