InsightSocial OpenAPI spec

The OpenAPI 3.1 spec for the InsightSocial API: 300+ GET endpoints for public data from 25 platforms (Instagram, TikTok, Facebook, LinkedIn, X/Twitter, Threads, YouTube, Reddit, Pinterest, Bluesky, Telegram, Twitch and more), behind one x-api-key header and one credit balance.

• File: openapi.json
• Live copy: https://api.insightsocial.app/v1/openapi.json (free, no key)
• Kept in sync: a GitHub Action fetches the live spec every day and commits it when it changes, so this repo's history doubles as a changelog of the API surface.
• Schema 2: the spec describes schema 2 (info.version 2.0.0), the only response shape since 2026-10-04: one typed shape per entity (post, profile, comment, transcript) on every platform. See Schema 2.

Use it

Generate a client, or hand it to an agent framework that builds tools from OpenAPI:

# Any generator works; for example
npx @openapitools/openapi-generator-cli generate \
  -i https://api.insightsocial.app/v1/openapi.json -g python -o insightsocial-client

Import it into Postman, Insomnia or Bruno with the same URL.

Every call needs your key in the x-api-key header (Authorization: Bearer is not read). Create one in the portal.

What the spec tells you

• Price per endpoint, in credits, in each operation's description and in its x-credits field. Metered endpoints show a range: the top is held when the call starts, and you are charged what the call used.
• Every parameter, with type, allowed values and an example.
• Free calls: failed calls, empty results, dry_run=1 and Idempotency-Key replays cost nothing. /v1/credits, /v1/endpoints and /v1/openapi.json are free.

For the same data as plain JSON with prices as fields, read the catalogue: GET https://api.insightsocial.app/v1/endpoints.

Related

• insightsocial/cli: CLI and MCP server (npx -y insightsocial init)
• insightsocial/skills: agent skills for Claude Code, Codex, Cursor and Gemini CLI
• Docs · Quickstart · API Explorer

Questions: support@insightsocial.app