Why does Weibo return 432 to my scraper?

Weibo answers 432 to requests that arrive without a valid visitor or login cookie. A first-time client gets 432 until it presents a SUB cookie from the short handshake Weibo's own web client performs, and copied cookies expire, so a scraper that worked yesterday can start getting 432 today. XTikAPI reads Weibo with 12 endpoints from $0.002 a call. A failed call is not charged, and a verified account gets $0.5 of trial balance.

Updated 2026-11-18

The usual fix and why it keeps breaking

Users of the open-source weibo-crawler are told to open m.weibo.cn in Chrome, copy the cookie from the Network tab, and repeat after it expires or the session changes. That works, and then it stops working, which is the maintenance cost.

Without cookies

weibo.posts.search searches posts by keyword; weibo.posts.detail and weibo.comments.list take a status_id; weibo.accounts.detail takes a uid. No cookie of yours is sent.

Why XTikAPI

  • One API key for Weibo and every other supported platform, with the same JSON shape: data holds the result, meta says what was billed.
  • A failed call or a timeout is not charged; the response says charged: false.
  • X-Max-Price caps what one call may cost, and the same Idempotency-Key within 24 hours is never billed twice.
  • Prepaid balance, no subscription. Balance never expires, and unused top-up money can be refunded within 14 days.

Endpoints

More about Weibo

Sources