UnifAPI Docs

API Reference

Every UnifAPI endpoint, auto-generated from the unified OpenAPI 3.1 spec.

UnifAPI exposes a single, AI-friendly HTTP surface across every provider. Pick a platform below to browse its endpoints.

  • Bilibili (哔哩哔哩) — Public-data Bilibili endpoints (Web surface).
  • Instagram — Public-data Instagram endpoints (V3 surface).
  • Kuaishou (快手) — Public-data Kuaishou / 快手 endpoints (App surface).
  • Lemon8 — Public-data Lemon8 endpoints (App surface).
  • LinkedIn — Public-data LinkedIn endpoints.
  • PiPiXia (皮皮虾) — Public-data PiPiXia / 皮皮虾 endpoints (App surface).
  • Reddit — Public-data Reddit endpoints (APP surface).
  • Threads — Public-data Threads endpoints (Web surface).
  • TikTok — Public-data TikTok endpoints.
  • Twitter / X — Public-data Twitter / X endpoints (Web surface).
  • Weibo (微博) — Public-data Weibo endpoints (Web-V2 surface).
  • Xiaohongshu (小红书) — Public-data Xiaohongshu / 小红书 endpoints (Web-V3 surface).
  • YouTube — Public-data YouTube endpoints (Web surface).
  • Zhihu (知乎) — Public-data Zhihu / 知乎 endpoints (Web surface).

All operations share the gateway conventions:

  • Auth via Authorization: Bearer <key> (forwarded to the upstream provider).
  • Closed-vocabulary error envelope ({ error: { type, message, request_id?, issues? } }) — see Errors.
  • List responses use { items, has_more, next_cursor } with opaque string cursors — see Concepts.

The machine-readable spec lives at /openapi.json (single source of truth).

Bilibili (哔哩哔哩) API

Public-data Bilibili endpoints (Web surface).