Admapix

Request Parameters

Interaction Flow

Follow these steps strictly after receiving a user request:

Step 1: Parse Parameters

Extract all possible parameters from the user's natural language. Read references/param-mappings.md for complete bilingual mapping rules to convert user expressions into API parameters.

Quick reference (supports both Chinese and English):

Step 2: Confirm Parameters

Must show parsed parameters before executing the search. Format:

📋 Search Parameters:

🔑 Keyword: puzzle game
🎬 Creative type: Video (010)
🌏 Region: Southeast Asia → TH, VN, ID, MY, PH, SG, MM, KH, LA, BN
📅 Date range: Last 30 days (2026-02-08 ~ 2026-03-10)
📊 Sort: First seen ↓
📄 Per page: 20

Confirm search, or need adjustments?

Rules:

• List all recognized parameters with both the original value and converted code
• Show defaults for unspecified parameters
• For region parameters, show both the region name and actual country codes

Step 3: Ask for Missing Parameters

If the user did not provide a keyword, ask:

What kind of ad creatives are you looking for? You can tell me:
• 🔑 Keyword (e.g. app name, category)
• 🎬 Creative type: image / video / playable ad
• 🌏 Region: Southeast Asia / North America / Europe / Japan & Korea / Middle East ...
• 📅 Time: last week / last month / custom
• 📊 Sort: newest / most popular (impressions)

Other parameters can use defaults, but inform the user in Step 2.

Step 4: Check API Key

Before executing the search, check if $ADMAPIX_API_KEY is set (via [ -n "$ADMAPIX_API_KEY" ] && echo "configured" || echo "not configured" — never print or output the API Key value).

If not set (empty), output this guidance and stop — do not continue with the search:

🔑 You need to configure an AdMapix API Key before searching.

1. Go to https://www.admapix.com to register and get your API Key
2. Run this command to configure:
   openclaw config set skills.entries.admapix.apiKey "YOUR_API_KEY"
3. Then try your search again 🎉

If set, continue to the next step.

Step 5: Build and Execute curl Command

After user confirmation, build the JSON body and call the API via curl.

Build rules:

• content_type fixed to "creative"
• generate_page fixed to true
• Only include user-specified parameters and non-default values
• Array parameters use JSON array format: "country_ids":["US","GB"]

Example:

curl -s -X POST "https://api.admapix.com/api/data/search" \
  -H "X-API-Key: $ADMAPIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content_type":"creative","keyword":"puzzle game","creative_team":["010"],"page":1,"page_size":20,"sort_field":"3","sort_rule":"desc","generate_page":true}'

Step 6: Send H5 Result Page Link

The page_url field in the API response is the server-generated H5 page path. Full URL: https://api.admapix.com{page_url}

Send message: Only send the following short message + H5 link. Do NOT append any text-format result list.

🎯 Found XXX ad creatives for "keyword" (page 1)
👉 https://api.admapix.com{page_url}

Say "next page" to continue | Say "video only" to filter

Strict requirement: the message contains only the lines above. Do not output a text list of search results. All results are displayed in the H5 page.

Notes:

• Pages auto-expire after 24 hours
• Each search/page turn generates a new page

Step 7: Follow-up Interactions

Possible follow-up commands and how to handle them:

• "next page" / "下一页": Keep all parameters, page +1, re-execute Step 5-6
• "video only" / "只看视频": Adjust creative_team, reset page to 1
• "change keyword to XXX" / "换个关键词": Replace keyword, optionally keep other params
• Adjust filters: Modify corresponding params, go back to Step 2 to confirm, then re-search

API Response Structure

{
  "totalSize": 1234,
  "page_url": "/p/abc123",
  "page_key": "abc123",
  "list": [{
    "id": "xxx",
    "title": "App Name",
    "describe": "Ad copy...",
    "imageUrl": ["https://..."],
    "videoUrl": ["https://..."],
    "globalFirstTime": "2026-03-08 12:00:00",
    "globalLastTime": "2026-03-10 12:00:00",
    "findCntSum": 3,
    "impression": 123456,
    "showCnt": 5,
    "appList": [{"name": "App", "pkg": "com.xxx", "logo": "https://..."}]
  }]
}

Output Guidelines

1. Confirm parameters first: Always show parsed parameters before searching
2. All links in Markdown format: [text](url)
3. End each output with next-step hints to guide continued interaction
4. Humanize impression numbers: >10K show as "x.xK", >1M show as "x.xM" (or Chinese equivalents if user speaks Chinese)
5. Respond in the user's language: Match the language the user is using
6. Be concise and direct: No small talk, just deliver data
7. Maintain context: Remember previous parameters when paging or adjusting filters — don't ask from scratch