Platforms
API integration scopes for 36 platforms
A reference catalog of 36 platforms grouped by channel. Inclusion does not prove completed integration or client delivery. Scope depends on permissions, account eligibility and project validation.
Social · 20
| Platform | Project focus | Access and feasibility |
|---|---|---|
| Xiaohongshu (RED) | brand approvals and note workflows | Validate account ownership, obtainable permissions and permitted access routes first. Product links, commercial labels, reporting and publishing need separate checks; login access does not prove publishing access. |
| TikTok | regional video review and app access | Validate publishing routes and visibility against app review status, account permissions and current official flows. Test-environment success does not establish public publishing access for production accounts. |
| Douyin | store accounts and video review | Supply the app owner, target accounts and requested actions to verify platform permissions and business review requirements individually. Store count alone does not determine publishing capacity. |
| YouTube | large uploads and channel access | Determine capacity using the client project’s actual quotas, scopes and verification status rather than a universal daily-upload estimate. Verify API success separately from public video availability. |
| Kuaishou | merchant assets and video workflows | Verify account type, application purpose and whether content and commerce capabilities require different permissions. Video submission access does not imply full store administration. |
| visual assets and brand approvals | Verify formats against the selected Meta login route, account type and actual app permissions. Do not carry forward outdated account-linking, media-count or publishing-frequency assumptions. | |
| campaign schedules and pause controls | Verify write permissions, account binding and media types, including the available scope of withdrawal and interaction actions. Queue acceptance is not proof of platform publication. | |
| X (Twitter) | campaign copy and API cost planning | Confirm the current API access plan, read/write permissions and charging basis in the client account. Do not base delivery commitments on old plan names or historical free quotas; validate media and text paths separately. |
| Bilibili | video handoff and episode tracking | Verify submission capabilities, asset licenses, categories and review conditions. Distinguish file transfer, platform processing and content review rather than treating them as one success state. |
| Threads | copy variants and brand review | Verify current Threads login, authorization and app requirements independently. Do not infer shared permissions or account conditions simply because Instagram is also a Meta product. |
| WeChat Channels | content handoff and access validation | Channels, Official Accounts and WeCom have different permissions. Validate access for the target account; retain manual execution when publishing access is unconfirmed rather than promising automation after QR login. |
| company pages and admin access | Identify whether the actor is a member or organization before checking product access, scopes and administrative rights. Access for one actor does not establish access for the other. | |
| Xigua Video | video series and production handoff | Verify the creator account, submission route and asset requirements. Similar accounts or assets do not establish interchangeable permissions across Douyin, Toutiao and Xigua. |
| Facebook Pages | regional Pages and store approvals | Confirm the target asset, required permissions and current Meta app requirements. Page visibility does not establish write access to personal accounts or advertising assets. |
| Haokan | video assets and task reconciliation | Confirm the current account portal, video capabilities and permitted access route. Product relationships do not prove shared APIs, indexing or guaranteed views. |
| product assets and destination links | Check account and app access, formats, destination availability and asset licenses. Content publishing permissions do not replace catalog or advertising access. | |
| Medium | publication workflows and authorship | Check current account integration entry points and publication permissions. Historical API documentation does not prove new accounts can obtain publishing access; recommendations and earnings are not promised. |
| Bluesky | account identity and content references | Check operations against the chosen authentication route and actual server. An open protocol does not remove rate limits or credential management; distinguish service access from protocol features. |
| Mastodon | instance differences and account scope | Check terms, version and permissions for each instance rather than assigning universal text or file limits. Distinguish an unreachable instance from a rejected publication. |
| Tumblr | blog sections and asset rights | Confirm target-blog permissions, content models and media rights. New and legacy post structures and reblog permissions may differ; validate samples before migration. |
Communities · 7
| Platform | Project focus | Access and feasibility |
|---|---|---|
| Zhihu | expert review and content revisions | Confirm whom the account represents, content rights and obtainable API capabilities. Question matching assists planning; it does not establish automatic publishing access, rankings or AI citations. |
| community rules and human approval | Check commercial-use conditions, app access and community rules. API access does not establish community permission or guarantee that bulk promotion will remain visible. | |
| Taobao Jianghu | access validation and merchant content | This directory retains the Jianghu name without equating it to other Taobao content products. The client must supply the actual portal and account samples to establish current service availability and API access. |
| SMZDM | product links and price evidence | Check merchant identity, submission routes and product-information rights. Validate price collection separately from submission access; the coordination system is not a bulk-review manipulation tool. |
| Dewu (Poizon) | product models and asset permissions | Verify actual content permissions and access routes for brand or merchant accounts, including trademark and asset licenses. Content workflows do not establish trading or authentication API access. |
| Xueqiu | specialist review and source records | Verify institutional eligibility, content licenses and permitted operations. Avoid return promises and do not describe the workspace as investment advice or automated stock recommendations. |
| Quora | question research and expert approval | Verify data-use conditions and current submission routes. The ability to answer manually does not establish an open posting API or guarantee AI citations or referral traffic. |
News & search · 7
| Platform | Project focus | Access and feasibility |
|---|---|---|
| WeChat Official Accounts | CMS articles and draft approvals | Check draft, publication and media access against account type, verification and actual permissions. Validate images and links using client samples rather than borrowing permissions from other WeChat products. |
| Baijiahao | article revisions and result records | Verify account formats and access routes, plus republication and originality-label requirements. Submission does not establish search indexing and cannot guarantee rankings. |
| Toutiao | editorial desks and format approvals | Verify account permissions and interfaces for each format. Check sources, covers and formatting for republished material without promising recommendation volume or revenue shares. |
| Dayuhao | asset rights and destination records | Confirm the current account portal, asset rights and permitted operations. Dashboard visibility does not establish API readability, and distribution destinations need verifiable receipts. |
| Sohuhao | press approvals and source tracking | Verify organization-account conditions, submission routes and republication requirements. A publish button does not prove an open publishing API, and search visibility is not a delivery promise. |
| NetEase Hao | editorial ownership and content formats | Verify account eligibility, submission routes for each format and attribution requirements. Without a platform receipt, editorial completion must not be recorded as publication. |
| Tencent Qiehao | publisher accounts and task receipts | Confirm the current portal, content permissions and result fields. Do not assume Qiehao, Official Accounts and Channels share authorization; destination outcomes require independent evidence. |
Local · 2
| Platform | Project focus | Access and feasibility |
|---|---|---|
| Dianping | store offers and merchant approvals | Verify merchant authorization, data-use boundaries and available interfaces. Merchant administration does not permit posting reviews on users’ behalf or promising review volume or rankings. |
| Google Business Profile | location ownership and update records | Verify project eligibility, location management rights and applicability of each operation. Viewing a listing does not establish management access to all locations or all content types. |
01 / Qualification
Confirm the actual account and app
List account ownership, application purpose and required operations. Validate the current platform requirements before committing to production scope.
02 / Authorization
No passwords, ever
Verify the platform-approved access route and granted permissions. Include credential storage, expiry, revocation and operator responsibilities in the proposed design.
03 / Compliance
We do not bypass platform controls
No simulated logins, no bulk account creation, no fabricated engagement. Publishing rhythm follows platform rate limits.
Access
How accounts are connected
Assess each account, application and business operation separately. Agree the access evidence before scoping publishing or data callbacks.
| Method | How it works | Assessment inputs |
|---|---|---|
| QR authorization | A QR code is an interaction method. Verify the issuer, granted permissions and platform approval; scanning alone does not prove publishing access. | Issuer, consent record, permitted operations and revocation |
| OAuth authorization | Use the official consent flow where available. Confirm the app, requested scopes, expiry and production access against the intended operation. | App ownership, scopes, callback and test environment |
| Entity permissions | Brands, stores and organization pages need the matching entity-level permissions. | Account type, entity ownership and administrator role |
| App review | Some platforms require an app review before publishing is enabled. | Review status, approved use case and production restrictions |
This page describes authorization paths only. Implementation details are discussed in the technical proposal.
Tell us your platform list
The list determines timeline and price more than anything else.