Bilibili Sanlian Ads MAPI Entry, Authorization And Routing

Problem

When an LLM drives Bilibili Sanlian Ads MAPI, failures often come from unclear authorization state, the wrong advertiser account, mixing v3 and v4 delivery structures, or guessing fields and enum values. This skill turns that entry point into a fixed workflow that reduces the risk of sending writes to the wrong account or ad model.

How It Works

It acts as the entry skill for Bilibili advertising tasks. First, it decides whether the request is conceptual and avoids loading credentials. If an API call is needed, it checks the local authorization file, requests client_id and client_secret when missing, runs the OAuth authorization flow, and persists the authorization record. It then resolves authorized subjects and advertiser accounts, and for write operations it shows the account name and account_id before asking for confirmation.

A key routing step is deciding whether the account uses Legacy v3 with campaign-unit-creative or Creative-driven 2.0 with project-media. These models are mutually incompatible: v3 and v4 endpoints cannot read or write each other's ads, and their reporting dimensions must not be mixed. After this choice, the task routes to delivery, material, reporting, finance, or other sub-skills.

Boundaries And Cautions

The skill requires sequential MAPI calls, stops and classifies errors on quota, throttling, authentication, or business failures, and does not blind-retry. Field names and enum values must come from each sub-skill's references/ files. It does not cover goods management, the industry product centre, brand information management, agency management, account qualifications, or related out-of-scope operations, which should be handled through Bilibili's developer documentation or the appropriate business APIs.