UnifAPI Docs

API Reference

Live public-data operations behind UnifAPI Skills, auto-generated from the unified OpenAPI 3.1 spec.

The API reference is the data layer behind UnifAPI Skills. Agents usually call these operations through MCP; developers can call the same live public-data endpoints over HTTP when productizing a workflow.

  • Amazon — Amazon creator storefronts: the creator's profile, social links, lists, curations and trending picks with prices.
  • Apple Music — Apple Music catalog search, plus artists, albums and songs by their Apple Music id.
  • Bluesky — Bluesky profiles, a profile's posts, and single posts.
  • Browser — Headless browser rendering.
  • Email — Free email filter endpoints.
  • Events — Live events search.
  • Facebook — Facebook pages and their posts, reels and events, post comments and transcripts, public groups, Marketplace listings, events and the Meta Ad Library.
  • GEO — AI answer visibility: live ChatGPT and Gemini answers, LLM mentions of a domain or keyword, the domains and pages AI answers cite most, and AI search volume.
  • GitHub — GitHub users and organizations with their repositories, pull requests, activity, followers and contribution graphs, plus trending repositories and developers.
  • Google Ads Transparency — Google Ads Transparency Center records: search advertisers, list the ads an advertiser runs, and look up a single ad.
  • Hacker News — Public-data Hacker News endpoints.
  • Hotels — Live hotel search and detail.
  • Instagram — Public-data Instagram endpoints.
  • LinkedIn — Public-data LinkedIn endpoints.
  • Linktree — Linktree pages with their links and social profiles.
  • Local Finder — Live Local Finder search — the expanded local-pack listing.
  • Maps — Live local business search.
  • News — Live news search.
  • Pinterest — Pinterest pins, pin search, a user's boards and the pins on a board.
  • Reddit — Reddit posts, comments, subreddits, users, feeds, trending searches and keyword search.
  • Rumble — Rumble channel videos, video search, video details, captions and comments.
  • SEO — Live SEO optimization evidence endpoints.
  • Snapchat — Snapchat public profiles, Spotlight videos and their comments.
  • SoundCloud — SoundCloud profiles, a profile's tracks, and single tracks.
  • Spotify — Spotify artists, albums and tracks by Spotify id, with followers, monthly listeners and play counts.
  • Telegram — Public Telegram channels and groups, a channel's posts, and single posts.
  • Threads — Threads profiles, posts, replies and reposts, plus user and keyword search.
  • TikTok — Public-data TikTok endpoints.
  • Truth Social — Truth Social profiles, a profile's posts, and single posts by URL.
  • Twitch — Twitch channels with their videos and stream schedule, and clips by URL.
  • Twitter / X — Public-data Twitter / X endpoints.
  • Yelp — Yelp business search, business details, reviews and photos.
  • YouTube — Public-data YouTube endpoints (Web surface).

How To Read This Reference

Use this section as the contract map for UnifAPI's live public-data layer. The API catalog is generated from route metadata in the gateway, then published here as human-readable documentation and as a machine-readable OpenAPI 3.1 file. That means the paths, parameters, response shapes, and error vocabulary here are the same surface an MCP-capable agent discovers before it calls data.

The practical workflow is simple: start from the Skill or product task, pick the platform records that carry the evidence, inspect the operation page for required identifiers, then call the endpoint through MCP or direct HTTP. The response envelope stays consistent across platforms, so an agent can combine a Reddit thread, a YouTube channel, an X profile, and a LinkedIn company record without learning four separate result formats.

Shared Guarantees

  • Public-data scope only: endpoints are designed for records visible on public platform surfaces, not private account actions.
  • One auth model: HTTP callers use Authorization: Bearer <key>; MCP callers authenticate through the hosted UnifAPI server.
  • One billing unit: usage is counted on returned records so exploratory agent runs and production integrations can estimate cost from the same metadata.
  • One error envelope: validation failures, upstream misses, rate limits, and billing states use the shared error vocabulary documented in Errors.

All live operations share the gateway conventions:

  • Auth via Authorization: Bearer <key> with a UnifAPI API key; provider credentials are managed by UnifAPI.
  • Successful responses use { request_id, data, pagination?, billing }; list operations return arrays in data plus opaque cursor pagination.
  • Errors use the closed-vocabulary { error: { type, message, request_id?, issues?, billing? } } envelope — see Errors.

For agent workflows, start with Skills and MCP integration. The machine-readable spec lives at /openapi.json (single source of truth).

On this page