What is a unified schema?
In social APIs, a unified schema means every successful response shares the same top-level shape. On Social Fetch that shape is { data, meta }, so logging, billing, and retries do not fork per platform. Nested payloads still differ by resource.
The envelope
data holds the platform payload (profile, posts, transcript, and so on). meta carries operational fields such as requestId, creditsCharged on metered routes, and version.
Errors use a typed error envelope with machine-readable codes. You branch on HTTP status and documented fields, not on whether one network returned null and another returned [].
Unified does not mean identical fields
A TikTok video and a LinkedIn company page do not share every nested key. Unified means the wrapper and ops metadata stay stable, and overlapping concepts use consistent naming where the domain overlaps.
Where a route documents lookupStatus, read it before you write warehouse rows. That field is part of the contract, not a TikTok-only quirk.
Why teams care
Without a shared envelope, every new platform forks logging, billing reconciliation, and retry policy. With one, you add a route under /platforms and keep the same requestId and creditsCharged handling.
Ask and MCP return the same wrapper, so an agent prototype and a typed cron share one parser. Full product page: /unified-schema. Error and lookup rules: /docs/errors. OpenAPI: /openapi.json and per-operation pages under /docs/api.
FAQ
Does Ask use the same schema?
Yes. POST /v1/ask returns the same envelope, plus data.routedOperation for the nested lookup.
Where is the OpenAPI?
/openapi.json on the site, and per-operation pages under /docs/api. The TypeScript SDK tracks that spec.
Does this cover all 17 platforms?
Yes. Marketplace operations across 17 platforms share the envelope. Auth and system routes follow the same docs conventions.