Fetch article stats api wechat mp

Run job:api.wechat-mp.fetch-article-stats through the looot API: 1 provider, from $0.01 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

Fetch article stats api wechat mp.

Job id api.wechat-mp.fetch-article-stats, in Social data (WeChat official accounts). As of 2026-10-01, 1 provider serve it through 1 tool. Run job:api.wechat-mp.fetch-article-stats and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

A job run takes shared input names; looot maps them to each provider’s own fields. See Job inputs.

Any other key you send passes through unchanged. Each tool’s own fields are on its page below.

Providers and prices

A call that fails at the provider costs $0. See What’s free.

Output

Shape of the run’s result, the expected shape, not yet checked against real answers:

{ code, data: { debug_id, read_num, star_num, show_like, show_read, show_star, debug_info, like_count, show_share, share_count, can_use_star, show_collect, collect_count, comment_count, get_data_succ, is_subscribed, show_old_like, verify_status, old_like_count, show_like_gray, comment_enabled, show_share_gray, friend_seen_info: { friend_info: unknown[] }, show_friend_seen, show_collect_gray, show_old_like_gray, original_content_num, friend_subscribe_count }, docs, time, params: { raw, url }, router, message, support, cache_url, time_zone, message_zh, request_id, time_stamp, cache_message, cach... ...

The shape is cut here. Signed in, looot inspect tikhub-api-wechat-mp-fetch-article-stats prints all of it.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:api.wechat-mp.fetch-article-stats","input":{"url":"https://example.com"},"wait":30}'

const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:api.wechat-mp.fetch-article-stats",
    input: {
      url: "https://example.com",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);

import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:api.wechat-mp.fetch-article-stats",
        "input": {
            "url": "https://example.com",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To pin one provider, send its tool id as endpointId instead of job:api.wechat-mp.fetch-article-stats.