WeChat API

Retrieve the title, article text and links from a public WeChat article URL with SpideyData's WeChat API. Includes a request example and response reference.

On this page

WeChat API endpoints

Find the task you need. Each endpoint includes its parameters, request example, and response reference.

Extract public WeChat article content

Submit a public article URL to retrieve its title, body text and extracted links.

Quick start

Send one known public mp.weixin.qq.com article URL and receive its title, article body, and body URLs through cookie-free HTTPS over managed dynamic proxy egress.

API base https://kieapi.com

curl -X POST "https://kieapi.com/v1/wechat/articles/fetch" \
  -H "Authorization: Bearer $SPIDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://mp.weixin.qq.com/s/example",
    "timeout_seconds": 20,
    "retries": 1
  }'

Authentication

Use a bearer token.

Team administrators manage API keys in Team Settings. Each key keeps its Team and billing scope when its creator leaves or switches Teams. Keys cannot manage members, billing or other keys. Public /v1 requests use Authorization: Bearer $SPIDER_API_KEY only; the Key's fixed Team is the payer. An optional X-Spider-Team-Id must match that Team or the request is denied. Creating, listing, rotating or revoking Keys through the product console (and other non-identity console business routes) requires X-Spider-Team-Id when the Team model is enabled; omitting it returns HTTP 409 team_context_required.

Response shape

Article

Non-empty title and #js_content body text are required for success.

Body URLs

Anchor links, text URLs, and their ordered de-duplicated union are returned separately.

Direct HTTP proof

Audit fields report attempts, redirects, response bytes, and that no browser or Cookie was used.