Admapix

AdMapix Intelligence Assistant

Get started: Sign up and get your API key at https://www.admapix.com

You are an ad intelligence and app analytics assistant. Help users search ad creatives, analyze apps, explore rankings, track downloads/revenue, and understand market trends — all via the AdMapix API.

Data disclaimer: Download/revenue figures are third-party estimates, not official data. Always note this when presenting such data.

Language Handling / 语言适配

Detect the user's language from their first message and maintain it throughout the conversation.

Rules: 1. All text output (summaries, analysis, table headers, insights, follow-up hints) must match the detected language. 2. H5 page generation: When using generate_page: true, pass the keyword in the user's language so the generated page displays in the matching language context. 3. Field name presentation:

• Chinese → use Chinese labels: 应用名称, 开发者, 曝光量, 投放天数, 素材类型
• English → use English labels: App Name, Developer, Impressions, Active Days, Creative Type

4. Error messages must also match: "未找到数据" vs "No data found". 5. Data disclaimers: "⚠️ 下载量和收入为第三方估算数据" vs "⚠️ Download and revenue figures are third-party estimates." 6. If the user switches language mid-conversation, follow the new language from that point on.

API Access

Base URL: https://api.admapix.com Auth header: X-API-Key: $ADMAPIX_API_KEY

All endpoints use this pattern:

# GET
curl -s "https://api.admapix.com/api/data/{endpoint}?{params}" \
  -H "X-API-Key: $ADMAPIX_API_KEY"

# POST
curl -s -X POST "https://api.admapix.com/api/data/{endpoint}" \
  -H "X-API-Key: $ADMAPIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{...}'

Interaction Flow

Step 1: Check API Key

Before any query, run: [ -n "$ADMAPIX_API_KEY" ] && echo "ok" || echo "missing"

Never print the key value.

If missing — show setup guide

Reply with EXACTLY this (Chinese user):

🔑 需要先配置 AdMapix API Key 才能使用：

>

1. 打开 https://www.admapix.com 注册账号

2. 登录后在控制台找到 API Keys，创建一个 Key

3. 拿到 Key 后回来找我，我帮你配置 ✅

Reply with EXACTLY this (English user):

🔑 You need an AdMapix API Key to get started:

>

1. Go to https://www.admapix.com and sign up

2. After signing in, find API Keys in your dashboard and create one

3. Come back with your key and I'll set it up for you ✅

Then STOP. Wait for the user to return with their key.

❌ DO NOT just say "please provide your API key" without the registration link — the user may not have an account. ❌ DO NOT ask the user to restart the gateway — config changes are hot-reloaded automatically.

Auto-detect: if the user pastes an API key directly in chat (e.g. sk_xxxxx)

Some users will paste their key in the conversation instead of running the command. In that case:

1. Run this command (replace {KEY} with the actual key):

openclaw config set skills.entries.admapix.apiKey "{KEY}"

2. Reply: ✅ API Key 已配置成功！ (or English equivalent), then immediately proceed with the user's original query.

❌ DO NOT echo/print the key value back. ❌ DO NOT ask "已配置了吗？" or wait for confirmation — just proceed.

Step 1.5: Complexity Classification — 复杂度分类

Before routing, classify the query complexity to decide the execution path:

Classification rule — count the API calls needed:

Simple (exactly 1 API call):

• Single search: "搜一下休闲游戏素材" → 1× search
• Single ranking: "iOS免费榜Top10" → 1× store-rank
• Single detail: "Temu的开发者是谁" → 1× unified-product-search
• Single metric: "Temu下载量" → 1× download-detail (after getting ID, but that's lookup+query=2, so actually Deep)

Deep (2+ API calls):

• Any query requiring entity lookup + data fetch: "Temu下载量" needs search→download = 2 calls → Deep
• Any analysis: "分析XX" → always multi-call → Deep
• Any comparison: "对比XX和YY" → always multi-call → Deep
• Any market overview: "XX市场分析" → always multi-call → Deep
• Any trend: "XX趋势" → always multi-call → Deep

In practice, only these are Simple:

• Direct keyword search with no analysis: "搜XX素材", "找XX广告"
• Direct ranking with no drill-down: "排行榜", "Top 10"
• Filter-options or param lookups

Default: If unsure, classify as Deep (prefer thorough over incomplete).

Execution paths:

→ Simple path: Continue to Step 2 (existing routing logic). At the end of the response, append a hint in the user's language:

• Chinese: 💡 需要更深入的分析？试试说"深度分析{topic}"
• English: 💡 Want deeper analysis? Try "deep research on {topic}"

→ Deep path: Call the Deep Research Framework.

This is a 4-step process. Do NOT use [[reply_to_current]] until the final step.

Step 0 — Validate API key before submitting:

Run this command first to verify the API key is valid:

curl -s -o /dev/null -w "%{http_code}" https://api.admapix.com/api/data/quota -H "X-API-Key: $ADMAPIX_API_KEY"

• If it returns 200 → key is valid, proceed to Step 1.
• If it returns 401 or 403 → key is invalid or account is disabled. Show this message and STOP:
• Chinese: ❌ API Key 无效或账号已停用，请检查你的 Key 是否正确。前往 https://www.admapix.com 重新获取。
• English: ❌ API Key is invalid or account is disabled. Please check your key at https://www.admapix.com
• Do NOT submit to deep research if validation fails — it will waste resources and always fail.

Step 1 — Submit the research task (returns instantly):

Run this exact command (only replace {user_query} and {additional_context}):

curl -s -X POST "https://deepresearch.admapix.com/research" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer test-local-token-2026" \
  -d '{"project": "admapix", "query": "{user_query}", "context": "{additional_context}", "api_key": "'"$ADMAPIX_API_KEY"'"}'

• project is always "admapix" — do NOT change this.
• query is the user's research question (in the user's language).
• context is optional — add useful context such as "用户是游戏公司，关注二次元赛道" if relevant. Omit or set to null if not needed.
• api_key passes the user's API key to the framework — always include it as shown above.

This returns immediately with:

{"task_id": "dr_xxxx-xxxx-xxxx", "status": "pending", "created_at": "..."}

Extract the task_id value for Step 2.

Step 2 — Poll until done (use this exact script, do NOT modify):

Run this exact command, only replacing {task_id}:

while true; do r=$(curl -s "https://deepresearch.admapix.com/research/{task_id}" -H "Authorization: Bearer test-local-token-2026"); s=$(echo "$r" | grep -o '"status":"[^"]*"' | head -1 | cut -d'"' -f4); echo "status=$s"; if [ "$s" = "completed" ] || [ "$s" = "failed" ]; then echo "$r"; break; fi; sleep 15; done

This script polls every 15 seconds and exits only when the task is done. It may take 1-5 minutes. Do NOT interrupt it, do NOT add a loop limit, do NOT abandon it.

• When it finishes, the last line contains the full JSON result. Proceed to Step 3.

Step 3 — Format and reply to the user with the framework's report.

CRITICAL RULES:

• Do NOT send [[reply_to_current]] before Step 2 completes — it will stop execution.
• NEVER fall back to manual analysis. The framework WILL complete — just wait for it.
• NEVER write your own polling loop. Use the exact script above.

Processing the response JSON:

The completed response has this structure:

{
  "task_id": "dr_xxxx",
  "status": "completed",
  "output": {
    "format": "html",
    "files": [{"name": "report.html", "url": "https://deepresearch.admapix.com/files/{task_id}/report.html", ...}],
    "summary": "- Temu近30天广告投放以拉美和东南亚为核心\n- 视频素材占比超过95%\n- ..."
  },
  "usage": {"model": "gpt-5.4", "total_tokens": 377289, "research_time_seconds": 125.2}
}

Do NOT paste the full report into the chat. Instead:

1. Take output.summary (already formatted as bullet points) and present it directly as the key findings 2. Append the report link from output.files[0].url: [📊 查看完整报告]({url}) 3. Add follow-up hints based on the summary content

If the task failed (status="failed"):

• The response will contain "error": {"message": "..."} with a user-friendly reason
• Present the error to the user and suggest they try again or simplify their query
• Do NOT try to manually replicate the analysis

Example output (Chinese):

📊 深度分析完成！

**核心发现：**
- AFK Journey 近30天投放覆盖全球，美国、墨西哥、巴西为Top3市场
- 视频素材占比约90%，图片约10%
- 投放媒体位以休闲游戏和工具类App为主（Blockudoku、Backgammon等）
- 2/18-2/23 与 3/14-3/16 出现投放峰值，可能对应版本更新或活动

👉 [查看完整报告](https://deepresearch.admapix.com/files/dr_xxxx/report.html)

💡 试试："和RAID对比" | "看看素材" | "日本市场详情"

If Step 1 returns an error with `"code": "api_key_required"`: The user's API key is missing or not configured. Output the same API key setup instructions from the "Check API Key" section above and stop.

If the framework is unreachable (connection refused/timeout on Step 1): Fall back to the existing Deep Dive logic (Step 2 → Deep Dive intent group).

---

Step 2: Route — Classify Intent & Load Reference

Read the user's request and classify into one of these intent groups. Then read only the reference file(s) needed before executing.

Rules:

• If uncertain, default to Creative Search (most common use case).
• For Deep Dive, read reference files incrementally as each step requires them — do NOT load all files upfront.
• Always read references/param-mappings.md when the user mentions regions, creative types, or sort preferences.

Step 3: Classify Action Mode

Default for Creative Search intent: Browse. Only use Analyze when the user explicitly asks for analysis/insights on the search results.

Browse mode rules:

• MUST set generate_page: true in the API request — this generates an H5 page where users can visually browse and preview creatives
• The H5 page is the primary result — it provides a much better experience than listing raw data in chat
• Do NOT list individual creatives in chat text — instead provide the H5 link and a brief summary (total count, top advertiser, creative type breakdown)

Step 4: Plan & Execute

Single-group queries: Follow the reference file's request format and execute.

Cross-group orchestration (Deep Dive): Chain multiple endpoints. Common patterns:

Pattern A: "分析 {App} 的广告策略" — App Ad Strategy

1. POST /api/data/unified-product-search → keyword search → get unifiedProductId 2. GET /api/data/app-detail?id={id} → app info 3. POST /api/data/app-distribution with dim=country → where they advertise 4. POST /api/data/app-distribution with dim=media → which ad channels 5. POST /api/data/app-distribution with dim=type → creative format mix 6. POST /api/data/product-content-search → sample creatives

Read api-product.md for step 1-2, api-distribution.md for step 3-5, api-creative.md for step 6.

Pattern B: "对比 {App1} 和 {App2}" — App Comparison

1. Search both apps → get both unifiedProductId 2. app-detail for each → basic info 3. app-distribution(dim=country) for each → geographic comparison 4. download-detail for each (if relevant) → download trends 5. product-content-search for each → creative style comparison

Pattern C: "{行业} 市场分析" — Market Intelligence

1. POST /api/data/market-search with class_type=1 → country distribution 2. POST /api/data/market-search with class_type=2 → media channel share 3. POST /api/data/market-search with class_type=4 → top advertisers 4. POST /api/data/generic-rank with rank_type=promotion → promotion ranking

Pattern D: "{App} 最近表现怎么样" — App Performance

1. Search app → get unifiedProductId 2. download-detail → download trend 3. revenue-detail → revenue trend 4. app-distribution(dim=trend) → ad volume trend 5. Synthesize trends into a performance narrative

Execution rules:

• Execute all planned queries autonomously — do not ask for confirmation on each sub-query.
• Run independent queries in parallel when possible (multiple curl calls in one code block).
• If a step fails with 403, skip it and note the limitation — do not abort the entire analysis.
• If a step fails with 502, retry once. If still failing, skip and note.
• If a step returns empty data, say so honestly and suggest parameter adjustments.

Step 5: Output Results

Browse Mode

If `page_url` is present in the response — use the H5 link as primary result:

Chinese:

🎯 共找到 {totalSize} 条"{keyword}"相关素材
👉 [查看完整结果](https://api.admapix.com{page_url})

📊 概览：
- 头部广告主：{name}（曝光 {impression}）
- 最活跃素材：{title} — 投放 {findCntSum} 天
- 素材类型：视频 / 图片 / 混合

💡 试试："分析 Top 10" | "下一页" | "和{competitor}对比"

If `page_url` is NOT present (fallback) — list top creatives directly with media links:

For each creative in the result list, extract and display:

• title or describe (strip HTML tags like <font>)
• appList[0].name (associated app, strip HTML tags)
• impression (humanized)
• findCntSum (days active)
• videoUrl[0] → show as clickable link [▶️ 播放视频](url)
• imageUrl[0] → show as clickable link [🖼 查看图片](url)
• videoTimeSpan[0] → video duration in seconds

Chinese fallback template:

🎯 共找到"{keyword}"相关素材，以下为 Top {N} 条：

1. **{title or describe}**
   📱 {appName} · 曝光 {impression} · 投放 {findCntSum} 天 · {duration}s
   [▶️ 播放视频]({videoUrl})

2. **{title or describe}**
   📱 {appName} · 曝光 {impression} · 投放 {findCntSum} 天
   [🖼 查看图片]({imageUrl})

...

💡 试试："分析 Top 10" | "下一页" | "和{competitor}对比"

English fallback template:

🎯 Found "{keyword}" creatives, here are the top {N}:

1. **{title or describe}**
   📱 {appName} · {impression} impressions · {findCntSum} days · {duration}s
   [▶️ Play video]({videoUrl})

...

💡 Try: "analyze top 10" | "next page" | "compare with {competitor}"

Key rules for fallback:

• MUST include video/image URLs — these are the most valuable part of the result
• Show up to 5 creatives per page to keep output readable
• Always strip HTML tags from title, describe, and appList[].name
• If a creative has no title or describe, use the app name as fallback title
• Humanize impression numbers (万/亿 for Chinese, K/M/B for English)

Analyze Mode

Adapt output format to the question. Use tables for rankings, bullet points for insights, trends for time series. Always end with Key findings section.

Compare Mode

Side-by-side table + differential insights.

Deep Dive Mode

Structured report with sections. Adapt language to user.

English example:

📊 {App Name} — Ad Strategy Report

## Overview
- Category: {category} | Developer: {developer}
- Platforms: iOS, Android

## Ad Distribution
- Top markets: US (35%), JP (20%), GB (10%)
- Main channels: Facebook (40%), Google Ads (30%), TikTok (20%)
- Creative mix: Video 60%, Image 30%, Playable 10%

## Performance (estimates)
- Downloads: ~{X}M (last 30 days)
- Revenue: ~${X}M (last 30 days)

⚠️ Download and revenue figures are third-party estimates.
💡 Try: "compare with {competitor}" | "show creatives" | "US market detail"

Chinese example:

📊 {App Name} — 广告策略分析报告

## 基本信息
- 分类：{category} | 开发者：{developer}
- 平台：iOS、Android

## 投放分布
- 主要市场：美国 (35%)、日本 (20%)、英国 (10%)
- 主要渠道：Facebook (40%)、Google Ads (30%)、TikTok (20%)
- 素材类型：视频 60%、图片 30%、试玩 10%

## 表现数据（估算）
- 下载量：约 {X} 万（近30天）
- 收入：约 ${X} 万（近30天）

⚠️ 下载量和收入为第三方估算数据，仅供参考。
💡 试试："和{competitor}对比" | "看看素材" | "美国市场详情"

Step 6: Follow-up Handling

Maintain full context. Handle follow-ups intelligently:

Reuse data: If the user asks follow-up questions about already-fetched data, analyze existing results first. Only make new API calls when needed.

Output Guidelines

1. Language consistency — ALL output (headers, labels, insights, hints, errors, disclaimers) must match the user's detected language. See "Language Handling" section above. 2. Route-appropriate output — Don't force H5 links on analytical questions; don't dump tables for browsing 3. Markdown links — All URLs in [text](url) format 4. Humanize numbers — English: >10K → "x.xK" / >1M → "x.xM" / >1B → "x.xB". Chinese: >1万 → "x.x万" / >1亿 → "x.x亿" 5. End with next-step hints — Contextual suggestions in matching language 6. Data-driven — All conclusions based on actual API data, never fabricate 7. Honest about gaps — If data is insufficient, say so and suggest alternatives 8. Disclaimer on estimates — Always note that download/revenue data are estimates when presenting them 9. No credential leakage — Never output API key values, upstream URLs, or internal implementation details 10. Strip HTML tags — API may return <font color='red'>keyword</font> in name fields. Always strip HTML before displaying to the user.

Error Handling

AdMapix — 广告情报与应用分析 Skill

English

一站式广告情报助手。通过自然语言搜索广告素材、分析应用、查看排行榜、追踪下载量/收入、获取市场洞察。

功能

• 素材搜索 — 按关键词、地区、媒体、素材类型搜索广告创意，支持 H5 可视化结果
• 应用分析 — 查询任意应用的详情、开发者信息、广告素材库
• 排行榜 — App Store / Google Play 官方榜单，推广排行、下载排行、收入排行
• 下载量与收入 — 追踪下载量和收入的时间趋势（第三方估算数据）
• 投放分布 — 分析应用在哪些国家、哪些媒体位、用什么素材类型投放广告
• 市场分析 — 按国家、媒体渠道、广告主、流量主维度的行业级洞察
• 深度分析 — 多维度综合报告，整合以上所有能力
• 深度研究 — AI 驱动的深度分析，适用于复杂查询（多应用对比、市场策略报告、趋势分析）。需要 2 个以上 API 调用的问题会自动触发，返回结构化 HTML 报告和核心发现

安装

npx clawhub install admapix

配置

1. 前往 www.admapix.com 注册并获取 API Key 2. 配置环境变量：

openclaw config set skills.entries.admapix.apiKey "你的ADMAPIX_API_KEY"

使用示例

安装配置完成后，直接对 AI 助手说：

支持 中文 和 英文 双语 — 助手会自动匹配你的语言。

深度研究 — AI 驱动的智能分析报告

面对复杂的分析需求，AdMapix 会自动激活 深度研究引擎 — 一个服务端 AI 研究系统，远超简单的 API 查询。

工作原理：

1. Skill 自动评估问题复杂度。简单查询（单次搜索、单个排行）直接处理；涉及跨维度分析的问题自动路由到深度研究引擎。 2. 研究引擎自主规划并执行多步调研 — 协调数十个 API 调用、交叉验证多个数据源、综合分析并提炼洞察。 3. 最终输出结构化 HTML 报告，附带核心发现摘要，可直接分享或用于进一步决策。

什么情况会触发深度研究：

• 多应用对比：「对比 Temu、SHEIN 和 Wish 的广告策略」
• 策略分析：「这款游戏在日本是怎么做用户获取的？」
• 市场情报：「东南亚休闲游戏广告市场概况」
• 趋势解读：「这个 App 上周下载量为什么暴涨？」
• 任何需要 2 个以上 API 调用或跨实体推理的问题

你会得到：

• 带图表和数据表格的结构化 HTML 报告
• 核心发现的高管摘要
• 跨维度洞察（地域 × 媒体 × 素材 × 时间）
• 基于竞品数据的可执行建议

研究引擎通常在 1-5 分钟内完成，取决于查询复杂度。报告在线托管，支持链接分享。

链接

• 官网：www.admapix.com
• GitHub：github.com/fly0pants/admapix

---

由 妙智盛 提供技术支持

AdMapix — Ad Intelligence & App Analytics Skill

中文文档

All-in-one ad intelligence assistant. Search ad creatives, analyze apps, explore rankings, track downloads/revenue, and get market insights — all through natural language.

Features

• Creative Search — Search ad creatives by keyword, region, media, creative type, with H5 visual results
• App Analysis — Look up any app's details, developer info, and ad creative portfolio
• Rankings — App Store / Google Play charts, promotion rankings, download rankings, revenue rankings
• Download & Revenue — Track download and revenue trends over time (third-party estimates)
• Ad Distribution — Analyze where and how an app advertises (countries, media placements, creative formats)
• Market Analysis — Industry-level insights by country, media channel, advertiser, and publisher
• Deep Dive — Multi-dimensional reports combining all of the above
• Deep Research — AI-powered deep analysis for complex queries (multi-app comparisons, market strategy reports, trend analysis). Automatically triggered for questions requiring 2+ API calls, returns structured HTML reports with key findings

Install

npx clawhub install admapix

Setup

1. Go to www.admapix.com to register and get your API Key 2. Configure:

openclaw config set skills.entries.admapix.apiKey "YOUR_ADMAPIX_API_KEY"

Usage Examples

After setup, just tell your AI assistant:

Supports both English and Chinese — the assistant responds in your language.

Deep Research — AI-Powered Intelligence Reports

For complex analytical queries, AdMapix automatically activates its Deep Research Framework — a server-side AI research engine that goes far beyond simple API lookups.

How it works:

1. The skill classifies your query by complexity. Simple lookups (single search, single ranking) are handled directly. Anything requiring cross-dimensional analysis is routed to Deep Research. 2. The research engine autonomously plans and executes a multi-step investigation — orchestrating dozens of API calls, cross-referencing data sources, and synthesizing findings. 3. Results are delivered as a structured HTML report with key findings summary, ready for sharing or further analysis.

What triggers Deep Research:

• Multi-app comparisons: "Compare Temu, SHEIN, and Wish's ad strategies"
• Strategy analysis: "How is this game acquiring users in Japan?"
• Market intelligence: "Southeast Asia casual game ad market overview"
• Trend interpretation: "Why did this app's downloads spike last week?"
• Any question requiring 2+ API calls or cross-entity reasoning

What you get:

• Structured HTML report with charts and data tables
• Executive summary with key findings
• Cross-dimensional insights (geo × media × creative × time)
• Actionable recommendations based on competitive data

The framework typically completes in 1–5 minutes depending on query complexity. Reports are hosted and shareable via link.

Links

• Website: www.admapix.com
• GitHub: github.com/fly0pants/admapix

---

Built by Miaozhisheng

Creative Search API / 素材搜索接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

---

1. Search — 素材搜索

POST /api/data/search

Search ad creatives across 5 content types. Supports H5 page generation.

Content Types

Request Body

{
  "content_type": "creative",
  "keyword": "puzzle game",
  "keyword_type": "",
  "is_new": false,
  "start_date": "2026-02-14",
  "end_date": "2026-03-16",
  "page": 1,
  "page_size": 20,
  "sort_field": "3",
  "sort_rule": "desc",
  "country_ids": [],
  "media_ids": [],
  "adfaction_ids": [],
  "device": [],
  "topic_type": [],
  "languages": [],
  "material_type": "",
  "trade_level1": [],
  "trade_level2": [],
  "trade_level3": [],
  "subject_type": [],
  "product_model": [],
  "product_type": [],
  "selling": [],
  "monetization": [],
  "pay_type": [],
  "company_location": [],
  "campaign_list": [],
  "ad_media_type": [],
  "appeal_type_list": [],
  "interaction_list": [],
  "material_tag": [],
  "material_removal_repeat": false,
  "demoad_formats": [],
  "web_tools": [],
  "material_top_limit": "",
  "gpt_search": null,
  "generate_page": false,
  "delivery": null
}

Key Parameters

Response

Note: totalSize may be null for keyword searches. Use pageIndex and pageSize for pagination.

{
  "pageIndex": 1,
  "pageSize": 20,
  "totalSize": null,
  "list": [
    {
      "id": "87f11b718e162ca06589f3c33ef99472",
      "title": null,
      "describe": null,
      "documentId": null,
      "findCnt": 1,
      "findCntSum": 1,
      "firstTime": "2026-03-16 13:44:54",
      "lastTime": null,
      "globalFirstTime": "2026-03-16 13:44:54",
      "globalLastTime": "2026-03-16 13:44:54",
      "imageFp": [],
      "imageUrl": [],
      "videoFp": ["80c15b563dded967090b0f5850f4941b"],
      "videoUrl": ["https://...video.mp4"],
      "playHtmlFp": [],
      "playHtmlUrl": [],
      "demoadCnt": 1,
      "appList": [
        {
          "id": "6498883328",
          "cnt": null,
          "impression": null,
          "name": "Tile Trip - Match <font color='red'>Puzzle</font> Game",
          "logo": "https://...logo.png",
          "geo": null,
          "pkg": null,
          "developer": "Oakever Games",
          "developerId": "1604529155",
          "productType": [1],
          "tradeLevel1": null,
          "tradeLevel2": null,
          "tradeLevel3": null
        }
      ],
      "sourceAppList": null,
      "originalUrl": null,
      "showCnt": 2802,
      "impression": 145354,
      "webSite": null,
      "demoadWebSite": null,
      "thumbnailConverUrl": ["https://...keyframe.jpg"],
      "videoTimeSpan": [60],
      "growthValue": null,
      "growthRate": null,
      "coverContent": null,
      "novel": null,
      "adSource": 9
    }
  ],
  "folderTotalSize": null,
  "newNum": null,
  "latestDate": null,
  "gptCorrect": {
    "sourceKeyword": "puzzle",
    "correctKeyword": null,
    "type": 3,
    "developers": [],
    "wrongs": [],
    "gptSxes": [],
    "slices": []
  },
  "filters": [],
  "page_url": "/p/abc123",
  "page_key": "abc123",
  "page_expires_at": "2026-03-19 12:00:00"
}

page_url/page_key/page_expires_at only present when generate_page: true.

⚠️ Important Notes

1. HTML tags in names: appList[].name may contain HTML highlight tags like <font color='red'>keyword</font>. Strip these before displaying to the user. 2. Null values: Many fields can be null — always handle null gracefully. 3. totalSize null: For keyword searches, totalSize is often null. The actual result count is reflected in list length per page.

Response Key Fields

---

2. Count — 素材计数

POST /api/data/count

Get total count, new count, and latest date for a single content type.

Request Body

Same as search (content_type + filter params). Only counting fields matter — page/sort are ignored.

Response

{
  "totalSize": 50000,
  "newNum": 1200,
  "latestDate": "2026-03-16"
}

---

3. Count All — 全类型计数

POST /api/data/count-all

Aggregate counts across all 5 content types. No request body needed.

Response

{
  "creative": { "label": "创意组合", "totalSize": 50000, "newNum": 1200, "latestDate": "2026-03-16" },
  "imagevideo": { "label": "图片/视频", "totalSize": 120000, "newNum": 3500, "latestDate": "2026-03-16" },
  "preplay": { "label": "试玩广告", "totalSize": 8000, "newNum": 200, "latestDate": "2026-03-15" },
  "demoad": { "label": "落地页", "totalSize": 30000, "newNum": 800, "latestDate": "2026-03-16" },
  "document": { "label": "文档素材", "totalSize": 5000, "newNum": 100, "latestDate": "2026-03-14" }
}

---

4. Distribute — 素材分布分析

POST /api/data/distribute

Analyze distribution of specific creatives by dimension.

Request Body

{
  "content_type": "creative",
  "dimension": "media",
  "ids": ["creative_id_1", "creative_id_2"],
  "start_date": "",
  "end_date": ""
}

Available Dimensions per Content Type

Note: Use advertiser as the dimension name (the API internally maps it to adfaction).

Use GET /api/data/distribute-dims to fetch this mapping dynamically.

---

5. Filter Options — 筛选枚举项

GET /api/data/filter-options

Returns all filter enum options in a single batch call (13 categories).

Response

IMPORTANT: Each item has both code (complex internal format) and ccode (simplified code). Always use `ccode` when passing filter values to search/query endpoints.

{
  "countries": [
    {"code": "毛里塔尼亚_2_MRT", "nameCn": "毛里塔尼亚", "nameEn": "Mauritania", "ccode": "MR", "icon": "https://...flag.png"}
  ],
  "mediaChannels": [
    {"code": "海外平台-101-Adcolony", "nameCn": "Adcolony", "nameEn": "Adcolony", "ccode": "101", "icon": "https://...icon.png"}
  ],
  "adTypes": [
    {"code": "adstyle_原生_1076682150_1076682150", "nameCn": "原生", "nameEn": "Native Ads", "ccode": "1076682150", "icon": null}
  ],
  "device": [
    {"code": "Android_2_1", "nameCn": "Android", "nameEn": "Android", "ccode": "1", "icon": "android"}
  ],
  "tradeLevel": [
    {"code": "601", "nameCn": "工具", "nameEn": "Tools", "ccode": "601", "icon": null}
  ],
  "productModel": [
    {"code": "1", "nameCn": "非游戏", "nameEn": "Non-game", "ccode": "1", "icon": null}
  ],
  "productType": [
    {"code": "app_1_1", "nameCn": "App", "nameEn": "App", "ccode": "1", "icon": null}
  ],
  "selling": [
    {"code": "5005_w2a", "nameCn": "W2A", "nameEn": "W2A", "ccode": "w2a", "icon": null}
  ],
  "subjectType": [
    {"code": "gold_0_1", "nameCn": "金币", "nameEn": "Gold", "ccode": "1", "icon": null}
  ],
  "topicType": [
    {"code": "传奇_9_64", "nameCn": "传奇", "nameEn": "Legend", "ccode": "90064", "icon": null}
  ],
  "languages": [
    {"code": "南非荷兰语_af", "nameCn": "南非荷兰语", "nameEn": "Afrikaans", "ccode": "af", "icon": null}
  ],
  "materialTag": [
    {"code": "AI_0_1", "nameCn": "AI", "nameEn": "AI", "ccode": "001", "icon": ""}
  ],
  "tradeLevel2": [
    {"code": "60301", "nameCn": "电商", "nameEn": "E-commerce", "ccode": "60301", "icon": null}
  ],
  "materialFormat": [
    {"code": "5006_100", "nameCn": "单图", "nameEn": "Single Image", "ccode": "100", "icon": null}
  ]
}

Filter Code Usage

Additional Response Field: tradeLevelTree

The response also includes tradeLevelTree — a hierarchical tree structure of all industry categories (level 1 → 2 → 3), useful for building category pickers or understanding the category hierarchy.

---

6. Content Detail — 素材详情

GET /api/data/content-detail

Get detailed information about a specific creative, or its related content (associated media, trends, profile, etc.).

Query Parameters

Related Types

Examples

# Get base info for a creative
GET /api/data/content-detail?content_type=creative&id=abc123

# Get related videos
GET /api/data/content-detail?content_type=creative&id=abc123&related=imagevideo&material_type=2

# Get trend data
GET /api/data/content-detail?content_type=creative&id=abc123&related=trend&start_date=2026-01-01&end_date=2026-03-16

---

7. Item Apps — 素材关联应用

POST /api/data/item-apps

Batch-fetch the associated apps for a list of creative IDs. Useful for enriching search results with app info.

Request Body

{
  "content_type": "creative",
  "ids": ["id1", "id2", "id3"]
}

Response

Returns a mapping of creative ID → app list:

{
  "id1": [
    {"id": "com.example.app", "name": "App Name", "logo": "https://..."}
  ],
  "id2": [
    {"id": "6498883328", "name": "Another App", "logo": "https://..."}
  ]
}

---

8. Screen Types — 单类筛选项

GET /api/data/screen-types?element_type=1

Fetch a single filter category by element type ID.

---

7. Page Config — 页面配置

GET /api/data/page-config?scope=search

Returns page layout configuration for the specified scope.

App Distribution API / 应用投放分布接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

These endpoints require a unified_product_id. Get it from unified-product-search first.

---

1. App Distribution — 应用推广分布

POST /api/data/app-distribution

Analyze an app's ad distribution across different dimensions.

Request Body

{
  "unified_product_id": "xxx",
  "dim": "country",
  "start_time": "",
  "end_time": "",
  "countries": [],
  "media_ids": [],
  "material_type": "",
  "index_type": 0
}

Dimensions

Response Examples

dim=country:

{
  "list": [
    {"code": "US", "name": "United States", "cnt": 500, "ratio": 0.35},
    {"code": "JP", "name": "Japan", "cnt": 300, "ratio": 0.21}
  ]
}

dim=trend:

{
  "list": [
    {"date": "2026-03-01", "cnt": 50},
    {"date": "2026-03-02", "cnt": 65}
  ]
}

dim=media (publisher apps / ad placements):

{
  "list": [
    {"id": "101", "name": "Block Blast Adventure Master", "cnt": 400, "ratio": 0.15},
    {"id": "102", "name": "Snake.io", "cnt": 250, "ratio": 0.09},
    {"id": "103", "name": "Solitaire", "cnt": 180, "ratio": 0.07}
  ]
}

These are the apps where the target app's ads are being shown (publisher side). When presenting this data, you can categorize them (e.g. casual games, tools, content apps) to provide more actionable insights.

---

2. Distribute Dims — 素材分布维度

GET /api/data/distribute-dims

Returns which distribute dimensions are available per content type. This is for the creative-level distribute endpoint (/api/data/distribute), not for app-distribution.

Response

{
  "creative": ["media", "advertiser", "app"],
  "imagevideo": ["media", "advertiser", "app", "country"],
  "preplay": ["media", "advertiser", "app"],
  "demoad": ["media", "advertiser", "app"],
  "document": ["media", "advertiser", "app"]
}

---

3. Global Promote — 全局推广分布

POST /api/data/global-promote

Analyze the global promotion distribution for one or more products across countries, media, or advertisers.

Request Body

{
  "ids": ["product_id_1", "product_id_2"],
  "dim": "country",
  "keyword": "",
  "sort_field": "15",
  "sort_rule": "desc"
}

Response

Returns distribution data for the specified dimension. Structure varies by dim.

Difference from app-distribution

• app-distribution — Analyzes a single app's ad placement distribution (where/how it advertises)
• global-promote — Analyzes one or more products' promotion footprint across the global market (country/media/advertiser breakdown)

---

Common Workflows / 常用工作流

"Temu 主要在哪些国家投广告？"

app-distribution(unified_product_id=id, dim="country")

"Temu 用了哪些广告渠道？"

app-distribution(unified_product_id=id, dim="media")

"Temu 的投放趋势怎么样？"

app-distribution(unified_product_id=id, dim="trend", start_time="2026-01-01", end_time="2026-03-16")

"Temu 在美国投了多少视频广告 vs 图片广告？"

app-distribution(unified_product_id=id, dim="type", countries=["US"])

Full app advertising profile (multi-call)

1. dim="country" → where they advertise (target countries) 2. dim="media" → which publisher apps carry their ads (ad placements) 3. dim="type" → what creative formats they use 4. dim="trend" → how ad volume changes over time 5. dim="lang" → which languages they target

Combine all 5 for a comprehensive advertising strategy overview.

Download & Revenue API / 下载量与收入接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

These endpoints require a unified_product_id. Get it from unified-product-search first.

---

1. Download Date Range — 下载量可用日期

GET /api/data/download-date

Returns the available date range for download data queries.

Response

{
  "startDate": "2023-01-01",
  "endDate": "2026-03-15"
}

Use this to validate date params before calling download-detail/download-country.

---

2. Download Detail — 下载量趋势

POST /api/data/download-detail

Fetch download trend data for a specific app over time.

Request Body

{
  "unified_product_id": "xxx",
  "query_start_date": "2026-02-14",
  "query_end_date": "2026-03-16",
  "compare_start_date": "",
  "compare_end_date": "",
  "country_st": [],
  "day_type": 1,
  "flag": true,
  "is_all": false
}

Response

Returns time series data:

{
  "list": [
    {"date": "2026-03-01", "download": 150000, "compareDownload": 120000},
    {"date": "2026-03-02", "download": 160000, "compareDownload": 125000}
  ]
}

---

3. Download Country — 按国家下载量

POST /api/data/download-country

Fetch download data broken down by country.

Request Body

Same as download-detail.

Response

Returns per-country breakdown:

{
  "list": [
    {"country": "US", "countryName": "United States", "download": 500000},
    {"country": "JP", "countryName": "Japan", "download": 300000}
  ]
}

---

4. Revenue Date Range — 收入可用日期

GET /api/data/revenue-date

Returns the available date range for revenue data queries.

Response

{
  "startDate": "2023-01-01",
  "endDate": "2026-03-15"
}

---

5. Revenue Detail — 收入趋势

POST /api/data/revenue-detail

Fetch revenue trend data for a specific app.

Request Body

{
  "unified_product_id": "xxx",
  "query_start_date": "2026-02-14",
  "query_end_date": "2026-03-16",
  "compare_start_date": "",
  "compare_end_date": "",
  "country_st": [],
  "day_type": 1,
  "flag": true,
  "is_all": false,
  "revenue_type": "ALL"
}

---

6. Revenue Country — 按国家收入

POST /api/data/revenue-country

Fetch revenue data broken down by country.

Request Body

Same as revenue-detail.

---

Common Workflows / 常用工作流

"Temu 最近下载量怎么样？"

1. unified-product-search(keyword="temu") → get unifiedProductId 2. download-date → confirm available range 3. download-detail(unified_product_id=id, query_start_date="2026-02-14", query_end_date="2026-03-16") → trend 4. Present trend data with insights

"对比 Temu 在美国和日本的收入"

1. Get unifiedProductId (step 1 above) 2. revenue-country(unified_product_id=id, ...) → per-country revenue 3. Filter & compare US vs JP data

"Temu vs SHEIN 下载量对比"

1. Search both apps → get both unifiedProductId 2. download-detail for each → two trend datasets 3. Present side-by-side comparison

Day Type Reference

Market Analysis API / 市场分析接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

---

Market Search — 市场分析搜索

POST /api/data/market-search

Analyze the advertising market from 5 different dimensions. Provides macro-level market intelligence.

Request Body

{
  "class_type": 1,
  "data_type": "1",
  "start_date": "",
  "end_date": "",
  "trade_level3": [],
  "country_level2": [],
  "media_ids": [],
  "device": [],
  "ad_company_location": [],
  "traffic_company_location": [],
  "page": 1,
  "page_size": 20
}

Dimensions (class_type)

Data Type

Note: Date format for this endpoint uses slashes (YYYY/MM/DD), not dashes.

Response

IMPORTANT: This endpoint returns a different structure from other endpoints. The response uses data_list (not list) and nested dot-notation field names.

Pagination fields: page_total (total pages), page_num (current page), page_size.

class_type=1 (Country) response:

{
  "data_list": [
    {
      "market_query.list.id": "ID",
      "query.country_info.s_code": "ID",
      "query.country_info.c_code": "ID",
      "query.country_info.country_name": "印度尼西亚",
      "market_query.list.raw_impression": 11578945855,
      "market_query.list.impression": "116亿",
      "market_query.list.impressionRatio": "13.64%",
      "market_query.list.rank": 1,
      "query.country_info.image": "https://...flag.png"
    }
  ],
  "page_total": 34,
  "page_num": 1,
  "page_size": 3
}

Key fields to extract:

• query.country_info.country_name — country name (Chinese)
• query.country_info.c_code — country code
• market_query.list.impression — impression count (pre-formatted string like "116亿")
• market_query.list.raw_impression — raw numeric impression count
• market_query.list.impressionRatio — percentage share
• market_query.list.rank — rank position

class_type=4 (Advertiser) response:

{
  "data_list": [
    {
      "market_query.list.market_query.list.advertiser": "275091615",
      "market_query.list.query.company_info.unified_company_name": "VGam.es",
      "market_query.list.query.company_info.unified_company_id": "275091615",
      "query.pkg_info.productName": "Math Crossword – Endless Fun",
      "query.pkg_info.productLogo": "https://...logo.png",
      "query.pkg_info.unifiedPkgId": "com.vgames.mathcrossword",
      "market_query.list.market_query.list.company_impression": "64亿",
      "market_query.list.market_query.list.raw_company_impression": 6449946845,
      "market_query.list.market_query.list.company_impressionRatio": "10.31%",
      "market_query.list.market_query.list.top1_app_impression": "64亿",
      "market_query.list.market_query.list.rank": 1
    }
  ],
  "page_total": 500,
  "page_num": 1,
  "page_size": 2
}

Key fields to extract:

• market_query.list.query.company_info.unified_company_name — company name
• query.pkg_info.productName — top product name
• market_query.list.market_query.list.company_impression — total impression (formatted)
• market_query.list.market_query.list.company_impressionRatio — market share %
• market_query.list.market_query.list.rank — rank position

---

Common Workflows / 常用工作流

"全球游戏广告市场哪个国家最大？"

{"class_type": 1, "data_type": "1"}

"美国市场最大的游戏广告主是谁？"

{"class_type": 4, "data_type": "1", "country_level2": ["US"]}

"电商App广告市场对比：东南亚 vs 北美"

Two queries: 1. {"class_type": 1, "data_type": "2", "country_level2": ["TH","VN","ID","MY","PH","SG"]} 2. {"class_type": 1, "data_type": "2", "country_level2": ["US","CA"]}

Compare total counts, top advertisers, media distribution.

Market overview combo (multi-call)

For a comprehensive market report on a segment: 1. class_type=1 → geographic distribution 2. class_type=2 → media channel breakdown 3. class_type=4 → top advertisers 4. class_type=5 → top publishers

Combine for a full market intelligence report.

---

Filter Codes

Use GET /api/data/filter-options to get valid codes for:

• trade_level3 — industry/sub-category codes
• country_level2 — country codes (use the ccode field, e.g. "US", "JP")
• media_ids — media channel IDs (use the ccode field, e.g. "101" for Adcolony)
• device — device type codes (use the ccode field, e.g. "1" for Android)

See references/param-mappings.md for common country/region mappings.

Product & Company API / 产品与公司接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

---

1. Unified Product Search — 统一产品搜索

POST /api/data/unified-product-search

Search for unified products (cross-platform aggregated apps). This is the primary entry point for finding apps/products.

Request Body

{
  "keyword": "temu",
  "type": 1,
  "page": 1,
  "page_size": 20,
  "start_date": "",
  "end_date": "",
  "sort_field": "3",
  "sort_rule": "desc",
  "unified_product_id": "",
  "unified_developer_id": ""
}

Note: country_ids, media_ids, and device also apply to product-search and company-search.

Response

{
  "pageIndex": 1,
  "pageSize": 20,
  "totalSize": 96,
  "list": [
    {
      "unifiedProductId": "1641486558",
      "unifiedProductName": "<font color='red'>Temu</font>: Shop Like a Billionaire",
      "unifiedCompanyId": "569338280",
      "unifiedCompanyName": "Temu",
      "productIds": ["com.einnovation.temu", "1641486558", "com.Temu_Team_Up.used_letgo_buy_app1"],
      "tradeLevel1": ["603"],
      "tradeLevel2": ["60301", "60303"],
      "tradeLevel3": ["6030102", "6030301"],
      "tradeLevel4": [],
      "showCost": 23236263827,
      "impression": 2412399002696,
      "materialUvCnt": 7451078,
      "productCnt": 3,
      "iconUrl": "https://...logo.png",
      "collectId": null,
      "formerNames": null,
      "adSource": 9
    }
  ],
  "folderTotalSize": null,
  "newNum": 0,
  "latestDate": null,
  "gptCorrect": null,
  "filters": null
}

⚠️ Important Notes

1. HTML tags in names: unifiedProductName may contain HTML highlight tags <font color='red'>keyword</font>. Strip these before displaying. 2. The unifiedProductId returned here is the key input for detail/distribution/download/revenue endpoints. 3. productIds contains platform-specific IDs (Android package name, iOS app ID).

Key Fields

---

2. Product Search — 产品搜索

POST /api/data/product-search

Search for individual products (platform-specific). Same request body as unified product search.

Response

Returns normalized product items (different structure from unified-product-search):

{
  "list": [
    {
      "id": "com.einnovation.temu",
      "unifiedProductId": "com.einnovation.temu",
      "name": "Temu: Shop Like a Billionaire",
      "logo": "https://...logo.png",
      "pkg": "com.einnovation.temu",
      "developer": "Whaleco Inc.",
      "developerId": "569338280",
      "os": "android",
      "tags": ["60301", "60303"],
      "impressionEstimate": 2412399002696,
      "materialCnt": 7451078,
      "firstTime": "2022-09-01",
      "lastTime": "2026-03-17",
      "adDays": 1293,
      "countries": ["US", "JP"],
      "mediaList": ["Facebook", "Google"],
      "selling": "w2a",
      "productType": "App"
    }
  ],
  "totalSize": 96
}

Key Fields

---

3. Company Search — 公司/开发者搜索

POST /api/data/company-search

Search for companies/developers. Same request body as unified product search.

Response

{
  "pageIndex": 1,
  "pageSize": 1,
  "totalSize": 7,
  "list": [
    {
      "unifiedCompanyId": "1773957248",
      "unifiedCompanyName": "<font color='red'>Bytedance</font> 字节跳动",
      "unifiedCompanyRegion": "CN",
      "uaList": [1, 2, 3],
      "showCost": 10768429037,
      "impression": 2844436033460,
      "collectId": null,
      "productIds": ["com.zhiliaoapp.musically", "com.ss.android.ugc.trill", "1235601864", "..."],
      "productCnt": 53,
      "downloadCnt": null,
      "hitDeveloper": false,
      "unifiedCompanyNameDefault": null,
      "developerList": [
        {"id": "640989321", "name": "Bytedance Pte. Ltd", "status": 0, "productCnt": 9, "collectId": null}
      ],
      "unifiedCompanyNameOrigin": "Bytedance 字节跳动",
      "adSource": 9
    }
  ]
}

Key Fields

---

4. App Detail — 应用详情

GET /api/data/app-detail?id={unifiedProductId}

Get comprehensive detail for a specific app/product.

Response

{
  "unifiedProductId": "com.einnovation.temu",
  "unifiedProductName": "Temu: Shop Like a Billionaire",
  "unifiedCompanyId": "569338280",
  "unifiedCompanyName": "Temu",
  "productIds": ["com.einnovation.temu", "1641486558", "com.Temu_Team_Up.used_letgo_buy_app1"],
  "tradeLevel1": ["603"],
  "tradeLevel2": ["60301", "60303"],
  "tradeLevel3": ["6030102", "6030301"],
  "tradeLevel4": null,
  "showCost": null,
  "impression": null,
  "materialUvCnt": null,
  "productCnt": 3,
  "iconUrl": "https://...logo.png",
  "collectId": null,
  "formerNames": null,
  "adSource": 9
}

Note: showCost, impression, materialUvCnt are null in app-detail (these are only available in search results). Use unified-product-search to get these metrics.

---

5. Developer Detail — 开发者详情

GET /api/data/developer-detail?id={unifiedCompanyId}

Get developer/company detail.

Response

{
  "unifiedCompanyId": "569338280",
  "unifiedCompanyName": "Temu",
  "unifiedCompanyRegion": "美国",
  "uaList": [1, 2, 3],
  "showCost": null,
  "impression": null,
  "collectId": null,
  "productIds": ["com.einnovation.temu", "1641486558", "com.Temu_Team_Up.used_letgo_buy_app1"],
  "productCnt": 6,
  "downloadCnt": null,
  "hitDeveloper": null,
  "unifiedCompanyNameDefault": null,
  "developerList": [
    {"id": "444696740", "name": "HY Dev LLC", "status": 0, "productCnt": 7, "collectId": null},
    {"id": "480100326", "name": "Temu", "status": 0, "productCnt": 2, "collectId": null}
  ],
  "unifiedCompanyNameOrigin": null,
  "adSource": 9
}

Key Fields

---

6. For Product List — 公司子产品列表

POST /api/data/for-product-list

Get individual products under a company (used in company search popover).

Request Body

{
  "unified_id": "xxx",
  "page": 1,
  "page_size": 10
}

---

6b. Product List — 子产品列表

POST /api/data/product-list

Get individual products (per platform) under a unified product.

Request Body

{
  "unified_product_id": "xxx",
  "page": 1,
  "page_size": 20
}

---

7. Product Agg List — 开发者产品聚合列表

POST /api/data/product-agg-list

Get aggregated products under a specific developer.

Request Body

{
  "unified_developer_id": "xxx",
  "page": 1,
  "page_size": 20
}

---

8. Product Content Search — 产品维度素材搜索

POST /api/data/product-content-search

Search for ad creatives specifically associated with a product.

Request Body

{
  "content_type": "creative",
  "unified_product_id": "xxx",
  "keyword": "",
  "page": 1,
  "page_size": 20,
  "start_date": "",
  "end_date": "",
  "sort_field": "3",
  "sort_rule": "desc"
}

Response

Same structure as /api/data/search response — pageIndex, pageSize, totalSize + list[] of creatives. See api-creative.md for full field documentation.

---

9. App Profile — 应用商店画像

GET /api/data/app-profile?id={productId}&type=1

Get app store profile and audience data.

Response

Returns store information, audience demographics, category rankings, etc.

---

10. Similar Apps — 相似/竞品应用

POST /api/data/similar-apps

Find apps with similar audiences or competitive overlap based on a package name.

Request Body

{
  "pkg": "com.einnovation.temu",
  "sort_field": "7",
  "sort_rule": "desc",
  "trade_level3": [],
  "device": [],
  "country_level2": []
}

Response

Returns normalized product list (same structure as product-search response), with an additional similarity field per item.

---

11. SDK Detail — SDK 集成详情

GET /api/data/sdk-detail?pkg={packageName}

Query which SDKs an app has integrated.

Response

Returns SDK integration details for the specified app. Returns {} if no data available.

---

12. Product Content Counts — 产品素材类型计数

POST /api/data/product-content-counts

Get the total creative count for a product across all 5 content types. Useful for showing a quick overview of a product's ad creative portfolio.

Request Body

{
  "unified_product_id": "com.einnovation.temu",
  "start_date": "",
  "end_date": ""
}

Response

{
  "creative": 1234,
  "imagevideo": 5678,
  "preplay": 90,
  "demoad": 345,
  "document": 67
}

---

⚠️ Common Pitfalls

1. HTML tags in names: Both unifiedProductName and unifiedCompanyName may contain <font color='red'>keyword</font> HTML tags when returned from search endpoints. Always strip HTML before displaying. 2. Null metrics in detail endpoints: app-detail and developer-detail return null for showCost, impression, materialUvCnt. These metrics are only available in search result lists. 3. ID types: unifiedProductId and unifiedCompanyId are strings, not integers. Some may look like iOS app IDs (numeric) while others are Android package names.

---

Common Workflow / 常用工作流

Finding an app's full data

1. Search → unified-product-search(keyword="temu") → get unifiedProductId 2. Detail → app-detail(id=unifiedProductId) → full app info 3. Creatives → product-content-search(unified_product_id=id, content_type="creative") → app's ads 4. Sub-products → product-list(unified_product_id=id) → iOS/Android versions

Finding a developer's portfolio

1. Search → company-search(keyword="ByteDance") → get unifiedCompanyId 2. Detail → developer-detail(id=unifiedCompanyId) → company info 3. Products → product-agg-list(unified_developer_id=id) → all their apps

Finding competitors for an app

1. Search → unified-product-search(keyword="temu") → get package name from productIds 2. Similar → similar-apps(pkg="com.einnovation.temu") → competitor list 3. Enrich → For each competitor, use app-detail or product-content-counts for deeper analysis

Quick app creative portfolio overview

1. Search → unified-product-search(keyword="temu") → get unifiedProductId 2. Counts → product-content-counts(unified_product_id=id) → counts per content type 3. Browse → product-content-search(unified_product_id=id, content_type="creative") → actual creatives

Ranking API / 排行榜接口

Base URL: https://api.admapix.com Auth: X-API-Key: $ADMAPIX_API_KEY

---

1. Store Rank — 应用商店排行

POST /api/data/store-rank

Fetch App Store / Google Play official rankings.

Request Body

{
  "market": "appstore",
  "rank_type": "free",
  "cat_type": "game",
  "cat_code": "games",
  "country": ["US"],
  "page": 1,
  "page_size": 20
}

Response

Note: Uses nested dot-notation field names.

{
  "totalSize": 25,
  "pageIndex": 1,
  "pageSize": 2,
  "maxDate": "2026-03-16",
  "list": [
    {
      "query.info.query.info.productNameEn": "Solitaire Associations Journey",
      "query.info.query.info.productNameCn": null,
      "query.info.query.info.productNameDefault": "Solitaire Associations Journey",
      "query.info.query.info.productLogo": "https://...logo.png",
      "query.info.query.info.unifiedPkgId": "6748950306",
      "query.info.query.info.developerId": 1049188906,
      "query.info.query.companyInfo.companyId": "1049188906",
      "query.info.query.companyInfo.companyName": "Hitapps Games LTD",
      "query.list.rank": 1,
      "query.list.id": "6748950306"
    }
  ]
}

Key fields to extract:

• query.info.query.info.productNameDefault or productNameEn — app name
• query.info.query.info.productLogo — app icon URL
• query.info.query.companyInfo.companyName — developer name
• query.info.query.info.unifiedPkgId — unified product ID (use this for detail/distribution queries)
• query.list.rank — ranking position

---

2. Generic Rank — 通用排行榜

POST /api/data/generic-rank

Unified endpoint for 6 ranking types based on ad intelligence data.

Request Body

{
  "rank_type": "promotion",
  "category_id": "6014",
  "date_type": 1,
  "page": 1,
  "page_size": 50,
  "start_date": "",
  "end_date": "",
  "country": [],
  "sort_field": "",
  "sort_rule": "desc",
  "day_mode": ""
}

Ranking Types

Response — varies by rank_type!

IMPORTANT: Different rank types return different response structures.

promotion / newapp / overseas response:

Uses nested dot-notation field names (same style as store-rank):

{
  "totalSize": 1000,
  "list": [
    {
      "query.info.query.info.productNameDefault": "App Name",
      "query.info.query.info.productLogo": "https://...logo.png",
      "query.info.query.info.unifiedPkgId": "123456",
      "query.info.query.companyInfo.companyName": "Developer Name",
      "query.list.rank": 1,
      "query.list.id": "123456"
    }
  ]
}

download response:

Uses flat field names:

{
  "totalSize": 505970,
  "list": [
    {
      "productId": "6448311069",
      "appCode": "6448311069",
      "appName": "ChatGPT",
      "developer": "OpenAI OpCo, LLC",
      "developerId": "620366005",
      "iconUrl": "https://...logo.png",
      "queryDownloadCnt": 78578987,
      "compareDownloadCnt": 85509701,
      "downloadGrowth": -6930714,
      "growthPercent": -8.11,
      "isAd": "1",
      "productCnt": 3
    }
  ]
}

Key fields:

• appName — app name
• queryDownloadCnt — download count in query period
• compareDownloadCnt — download count in compare period
• downloadGrowth — absolute growth
• growthPercent — growth percentage (negative = decline)

revenue response:

Similar flat structure to download, with revenue-specific fields.

Rank Type Details

promotion — Ranks apps by advertising intensity. "Which apps are spending the most on ads?"

• Supports day_mode: "D3" (3 days), "D7" (7 days), "D30" (30 days)
• Advanced filter params (optional): keyword, trade_level1/2/3, subject_type, topic_type, product_model, product_type, selling, monetization, pay_type, company_location, campaign_list, media_ids, device

download — Ranks apps by estimated download volume. "Which apps are downloaded the most?"

• Includes auto-calculated compare period for growth calculation
• Advanced filter params (optional): trade_level1/2/3, subject_type, topic_type, product_model, product_type, selling, monetization, pay_type, company_location, media_ids, device
• ⚠️ Download/revenue figures are third-party estimates

revenue — Ranks apps by estimated revenue. "Which apps earn the most?"

• Same advanced filter params as download
• ⚠️ Revenue figures are third-party estimates

newapp — Tracks newly launched apps. "What new apps just launched?"

overseas — Tracks Chinese companies' apps in global markets. "Which Chinese apps are going overseas?"

drama — Tracks short drama / content apps. "What's trending in short drama?"

---

3. Store Categories — 商店分类

GET /api/data/store-categories

Fetch available app store categories for use with store-rank.

---

4. Store Countries — 商店国家列表

GET /api/data/store-countries

Fetch available countries for store ranking filter.

---

User Intent Mapping / 用户意图映射

Parameter Mapping Reference / 参数映射参考表

Creative Type (creative_team) / 创意组类型

Combination rule: Three-digit code represents "image_count - video - playable". E.g. "110" = 1 image + video + no playable.

Region → Country Code Mapping / 地区 → 国家代码映射

Common Country Quick Reference / 常见单个国家速查

Sort Options / 排序方式

Date Range Calculation / 时间范围计算

Date format: YYYY-MM-DD (e.g. 2026-03-10)

Page Size / 每页数量