Bilibili Sanlian Ads Material Management

Problem It Solves

Managing Bilibili Sanlian Ads materials is more than uploading files. Images must meet placement-specific format and dimension constraints, videos need asynchronous transcoding and archive creation, tags help organize large material libraries, and cross-account delivery should avoid duplicate uploads. This skill turns the Bilibili Sanlian Ads material management workflow into a practical operating guide for engineers who need to upload, verify, tag, and push ad assets reliably.

How It Works

• Image materials: Supports uploading from a file or via upload_pic_with_url. Before uploading, it recommends checking the existing image list so an already present image is not re-uploaded as a duplicate.
• Video materials: First requests a pre-signed URL through MAPI, then performs an external PUT to that storage URL, then creates archives and polls processing progress. The external PUT is not a MAPI call, should not include the Bearer token, and does not consume MAPI quota.
• Material tags: Supports creating, listing, updating, and deleting tags, as well as binding tags to materials. This is useful for organizing and retrieving assets in large advertiser accounts.
• Material push: Can bind a material to other advertiser accounts so the same asset can be reused without repeated uploads. Because this writes to other accounts, the target account list should be explicitly confirmed.
• Response handling: MAPI business success or failure is usually carried in the response body, not the HTTP status. Bulk endpoints report per-item results, so each item must be inspected rather than relying on a successful envelope.

Boundaries And Caveats

This skill focuses on material management rather than final ad creation. In legacy creative flows, materials may be referenced directly in the creative save request. In creative-driven 2.0, materials must become a referenceable media_id; local videos rely on the retained file_md5 from the upload flow. A valid access_token and advertiser account_id are required before use, and deletes of images, deletes of tags, and cross-account pushes should be checked for impact before execution.