Bilibili Sanlian Ads Creation Metadata Lookup

Problem

Bilibili Sanlian ad save requests depend on account-specific enum values and resource IDs. Promotion purpose, promotion content, optimization targets, targeting, placements, landing pages, and materials are often valid only for a particular advertiser account and delivery context. Guessing these values can cause save failures or create an unintended ad configuration.

How It Works

This skill is a read-only metadata lookup workflow for checking what can be selected before composing a save request. For MAPI calls, confirm a valid access_token and advertiser account_id, then send Authorization: Bearer {access_token} and X-Call-Source: sanlian-skills. Follow the dependency chain:
- 507 campaign promotion purposes
- 512 unit promotion content
- 513 and 522 optimization targets and two-stage bid ranges
- 520 targeting dimensions
- 514, 519, 518, 515, 516, 517, and 1697 promotion objects such as apps, games, goods, live rooms, reservations, mini apps, and mini games
- 527 legacy creative placements; 2.0 placements come from template-group endpoints in the delivery skill
- 531, 529, 530, 532–535, 1829, 537, 1887, 1942, and 1722 archives, dynamics, playable materials, landing pages, selling points, and archive components

Query one endpoint at a time, inspect the response, and reuse results within the same account and task. Empty results mean the account cannot use that resource; do not substitute hard-coded values. The public archive-information helper uses api.bilibili.com/x/web-interface/view, does not require advertiser context, and should not automatically trigger MAPI material lookups.