SocialQuery API Documentation
SocialQuery API — unified social media data for developers and AI agents
One API key, one consistent response format, 68 platforms, 646 endpoints.
SocialQuery gives teams a single social data API that normalizes results from 68 platforms into one dependable schema. Build one integration, query every source, and receive computed fields like engagement_rate and estimated_reach with each response.
The catalog covers public sources that reach more than 10 billion monthly users, including TikTok, Instagram, YouTube, Facebook, Reddit, LinkedIn, X, and research platforms.
API Reference
The reference is generated from the same OpenAPI document that powers the public API. Browse operations by platform, inspect parameters, compare credit costs, and copy request examples without leaving the docs.
Open API ReferenceWhy use a unified API?
One parser
Every source returns a predictable envelope with data, request metadata, credits, and cache state.
One key
Route production calls through the same API key and header instead of juggling provider credentials.
One billing model
Credit costs are visible before you call and returned after each request.
One agent surface
OpenAPI and markdown resources let AI tools discover the same operations as your developers.
Which platforms does SocialQuery support?
SocialQuery supports social networks, search engines, review sources, commerce catalogs, app stores, developer communities, and research tools.
Frequently asked questions
How do I authenticate?
Send your server-side API key with the x-api-key header. Keep production keys out of browsers and public repositories.
What does a response include?
Each response includes success state, platform, endpoint, data, credits, cache metadata, and a request id.
Can AI agents use these docs?
Yes. The docs, OpenAPI file, markdown exports, and llms resources describe the same operation catalog.
Do cached responses cost credits?
The response metadata tells you whether a result came from cache and how many credits were charged.