Miniapp Media Downloader

Use Dayu's FastAPI media resolver for WeChat Channels, Douyin, and Xiaohongshu share-link parsing. Use when an agent needs to call the public Swagger/OpenAPI resolver, obtain or apply a distribution key, parse share text into direct CDN media URLs, handle missing-key QR-code contact responses, or integrate a mini-program/downloader workflow without proxying media bytes through the application server.

Service

Use Dayu's public resolver API:

text

https://www.aluowang.top/threeApp

Docs:

text

https://www.aluowang.top/threeApp/docs

OpenAPI:

text

https://www.aluowang.top/threeApp/openapi.json

The resolver supports:

• WeChat Channels / 视频号
• Douyin / 抖音
• Xiaohongshu / 小红书

It returns upstream media URLs. Clients should download media directly from returned CDN URLs instead of proxying video or image bytes through the application server.

Access

POST /api/resolve requires:

text

X-Distribution-Key: <key>

If the key is missing or invalid, show the returned error, contact, and qrUrl. Do not invent access instructions.

The service contact is:

text

helloaigc2023

API Flow

1. Check health:

bash

curl "https://www.aluowang.top/threeApp/health"

2. Inspect Swagger/OpenAPI:

text

https://www.aluowang.top/threeApp/docs
https://www.aluowang.top/threeApp/openapi.json

3. Resolve one share link:

bash

curl -X POST "https://www.aluowang.top/threeApp/api/resolve" \
  -H "Content-Type: application/json" \
  -H "X-Distribution-Key: $DISTRIBUTION_KEY" \
  -d '{"url":"paste share text or URL here"}'

4. Resolve multiple share links:

bash

curl -X POST "https://www.aluowang.top/threeApp/api/resolve" \
  -H "Content-Type: application/json" \
  -H "X-Distribution-Key: $DISTRIBUTION_KEY" \
  -d '{"urls":["https://example.com/one","https://example.com/two"]}'

Response Handling

Expect a response shape like:

json

{
  "ok": true,
  "mode": "cookie",
  "resolved": [
    {
      "platform": "wechat_channels",
      "platformName": "视频号",
      "mediaType": "video",
      "title": "title",
      "author": "author",
      "downloadUrls": ["https://cdn.example/video.mp4"],
      "videoUrl": "https://cdn.example/video.mp4",
      "h264Url": "https://cdn.example/h264.mp4",
      "imageUrls": []
    }
  ],
  "failed": []
}

Missing or invalid key may return:

json

{
  "ok": false,
  "error": "请联系大瑜 helloaigc2023，转我一杯咖啡钱，开通三个平台直接下载。",
  "contact": "helloaigc2023",
  "qrUrl": "https://gpt-iamegs2.oss-cn-beijing.aliyuncs.com/qr-wechat.jpg"
}

Platform Notes

• For WeChat Channels, prefer h264Url for playback and saving when present.
• For Xiaohongshu image notes, use imageUrls and save images one by one.
• For Douyin video notes, use downloadUrls[0] or videoUrl, preserving fallback URLs when available.
• Never route video bytes through a backend proxy as a workaround for client download restrictions.

Safety

• Do not publish or log distribution keys.
• Do not publish or log cookies, passwords, or full tokenized CDN URLs.
• Treat returned media URLs as temporary and platform-owned.