B站三连广告-广告元数据

概述

Bilibili Sanlian Ads — Creation Configuration Lookup (创编配置查询)

Every ad save request is full of IDs and enum values that are only valid for a specific account, promotion purpose, promotion content or placement. This skill is how you obtain them. It is a read-only skill: it resolves what may be selected, and never creates or modifies an ad.

These lookups are shared by both delivery structures. The same endpoints feed legacy campaign/unit/creative saves and creative-driven 2.0 project/media saves. Two exceptions run the other way — the 2.0 template-group endpoints live in bilibili-sanlian-ads-delivery, and legacy creative placement (527) does not apply to 2.0, where placement is expressed through promotion_scene.

Usage Rules

• For MAPI metadata calls, confirm a valid access_token and advertiser account_id first; use bilibili-sanlian-ads when either is missing. The public archive-information lookup is independent and needs neither value.
• Every MAPI call goes through [scripts/mapi.sh](scripts/mapi.sh) (on Windows use py -3 scripts/mapi_client.py) — call <METHOD> <path> [--query-file q.json] [--body-file body.json]. It loads and refreshes the token, attaches the headers described below, enforces Rule 1 pacing, and applies the shared conservative error decision tree. It returns that classification with the raw response; endpoint-specific success and partial-success semantics still come from the reference below. Do not hand-write curl, requests or fetch for a MAPI call, and never fan out across accounts or objects in parallel.
• The public archive-information lookup is not MAPI and must not go through scripts/mapi.sh call, which would attach the advertiser token and refuse the path anyway. Use an ordinary HTTP client against https://api.bilibili.com/x/web-interface/view, with no Bearer token and no X-Call-Source. That host applies risk control: a default scripting User-Agent is rejected with HTTP 412 (request was banned), so send a browser-shaped User-Agent. Keep long IDs as strings.
• MAPI base domain is https://cm.bilibili.com/takumi/api; MAPI calls use Authorization: Bearer {access_token}, X-Call-Source: sanlian-skills and X-Sanlian-Skills-Version: 3.0.4. The linked Bilibili public archive-information helper is not MAPI and requires none of those headers.
• Query these before composing a save request, not after it fails. A guessed enum or resource ID either fails the save or, worse, saves something the user did not intend.
• Before any ad-creation workflow, open [references/creation-field-source-map.md](references/creation-field-source-map.md). It maps each selectable save value to a lookup, a previous verified result, explicit user input, or an out-of-scope dependency. Do not compose the final save while any populated value has an unknown source.
• Open the matching reference before composing any request. Do not invent parameter names, and do not assume a lookup returns everything — most are filtered by account, promotion purpose, promotion content or placement, and their results change with those inputs.
• Follow the sequential-call and error-stop discipline in bilibili-sanlian-ads. Query one endpoint at a time, and do not start the next request until the previous one has completed and its response has been checked.
• Cache per account and reuse within a task. Promotion purposes, optimization targets, targeting dimensions and placements do not change between two calls a second apart. Re-querying the same lookup in a loop is the most common waste in this skill.
• Never treat an empty result as a reason to fall back to a hard-coded value. Empty means the account cannot use that resource — report that to the user.

When To Use

Lookup Order

The lookups form a dependency chain — later ones need values produced by earlier ones. Following the order avoids most save failures.

Confirm the user's business choice at each dependency boundary. Do not prefetch every metadata endpoint “just in case”; query only the branch needed by the confirmed promotion purpose, content, targeting and material type.

1. Promotion purpose (507) for the campaign or project.
2. Promotion content (512) — depends on the promotion purpose.
3. Promotion object — depends on the promotion content: app (514), game (519), goods (518), live room (515), live reservation (516/517), B mini app or mini game (1697), WeChat mini program or mini game (22734).
4. Optimization target (513) and, for two-stage bidding, the minimum bid range (522) — both depend on the promotion purpose and content.
5. Targeting dimensions (520) for the unit or project.
6. Placement: legacy uses creative placement (527); 2.0 uses promotion_scene from the template group endpoints in bilibili-sanlian-ads-delivery.
7. Deliverable material — archives, dynamics, local videos, playables — filtered by the placement and promotion content chosen above.
8. Creative accessories: landing page (537), paused-ad landing page (1887), selling point (1942), archive components (1722).

A resource must be consistent with the placement, template, promotion content, material type and audit requirements. Inconsistency is rejected at save time, or passes save and then fails audit.

Notes That Save A Debugging Cycle

• B mini apps and B mini games come from one endpoint (1697), distinguished by sort — sort=0 for mini apps, sort=2 for mini games. There is no separate mini-game endpoint; an older standalone one was retired.
• WeChat mini programs and mini games come from 22734, not 1697. One endpoint covers mini games, short dramas, novels and others (type 1–4). It returns account-owned assets by default; pass owner_type=2 for assets of the account's organization (no team_id needed). The two sources are never merged in one call. state=1 means online only — it is not audit approval and not a guarantee of deliverability; check audit_status.
• Selling points (1942) can list every type at once. content_type=0 or omitted returns all types and ignores content_id; for one type, pass several content_id values comma-separated. product_name_like filters by product name, and skip_extra_info=true skips images and tags for a lighter list.
• 530 ctime_from / ctime_to are 13-digit millisecond timestamps. A 10-digit seconds value is read as milliseconds, lands in 1970 and returns nothing. The window filters on when this account's archive record was created, not on the returned video.ctime (the MD5-level first-ingest time, which can be months earlier); never build a window from video.ctime. To find one video, prefer bvid / aid / keyword.
• For arc_type=7 on 531, omit task_id to page through all partner archives authorized to the account. Supply up to 100 comma-separated task IDs only when filtering by task; continue through the returned total_count with page and size.
• Archive and local-video lookups also return media_id for creative-driven 2.0. On 531 the field is absent when the material is not yet registered; on 530 it is the string "0". Use it when present, otherwise register through bilibili-sanlian-ads-delivery.
• video.material_id from 530 is not a media_id. It is the creative-centre material ID, a different ID space. Never substitute one for the other.
• Dynamics have four separate sources (532–535) for different origins — available MIDs, dynamics under a MID, manually bound, and Huahuo commercial. They are not interchangeable; pick by where the dynamic came from.
• Content usually has to be authorized before it is deliverable. If an expected archive, dynamic or Huahuo order does not appear in these lookups, the missing piece is normally authorization, not the lookup — see bilibili-sanlian-ads-assets.
• Components must exist before they can be selected. Story components, comment conversion components and native anchors are created in bilibili-sanlian-ads-assets; 1722 only reports how an archive is currently configured.
• Uploading material is a different skill. Use bilibili-sanlian-ads-materials to upload or import images and videos. This skill only reports what is already deliverable.
• The public archive-information helper is a standalone public-data query. It returns public video identity and descriptive information. It does not require an advertiser account, does not report advertising authorization or deliverability, and must not automatically trigger 531 or any other MAPI call.

Reading Responses And Errors

Business success or failure is carried in the response body, not the HTTP status. On any error or unclear outcome, stop and run the main skill's cold re-check and support-packet workflow. Do not retry with altered parameters or continue to a later lookup to discover what the API wants.

Goods list [518](references/518_获取商品列表.md) returns extra_outer_id (the goods ID recorded in Ali for UDS goods). It uses the same endpoint as goods-management list [643](../bilibili-sanlian-ads-assets/references/643_获取商品列表.md). The current implementation does not filter by extra_outer_id; use supported source, outer_id or item_id filters. For goods creation/editing, route to bilibili-sanlian-ads-assets: source=113 requires non-empty extra_outer_id and url_type=1.

Source Document Index

Synced from mapi/product/docs/开发者中心/MAPI接入/创编配置查询/ and 查询工具/. doc_id matches the article ID on the developer site.

Supporting Public Lookup