What are Bilibili's 412 error and wbi? (2026)
They are two things. 412 is an HTTP status that open-source tools report as Bilibili's risk control stopping a request. wbi is a signature on some of Bilibili's web requests, seen in addresses like /x/space/wbi/arc/search. With a data API you handle neither: a page of search is $0.0020, and you send only your key and a keyword. DataXAPI reads Bilibili with 9 endpoints, from $0.0020 a call; a failed call is not charged.
Updated 2026-11-04
Why you run into them
They come up when your own program reads Bilibili. The yutto project's issues show both sides: one reports 412 on a video-details address that did not happen on the wbi one, and another reports -352 and then 412 on an account's videos at somewhat higher rates, depending on the IP and the session rather than on which account was read. So a correct signature alone does not rule out a 412. How the signature is worked out is not something we cover.
If you would rather not deal with them
Each job is one call at $0.0020: bilibili.videos.search, bilibili.videos.get, bilibili.videos.comments.list and bilibili.users.videos.list. No signature, cookie or proxy of yours. A failed call is not charged, and 1,000 calls come to $2.
Endpoints
Each with its price; every page has the parameters, the fields and a recorded response.
Sources
What this page says of other services is from their own pages and documents, read on 2026-11-04. Prices and features change: check the source before you decide.