What is requestId?
requestId is Social Fetch's correlation ID for a single API call. Successful responses put it on meta.requestId; error responses include it in the typed error envelope. Support and logs start there, not with "it failed sometime yesterday."
How to use it
Log it on every response. Attach it to user-facing error reports. Include it when you email support or open a ticket.
You can also send X-Request-Id on the way in; if present we preserve it when valid, otherwise we mint one. See observability notes in the docs and reliability page.
What it is not
It is not a billing invoice ID. For spend, use meta.creditsCharged plus your own ledger and /v1/balance.
It is not a substitute for idempotency keys on writes. Social Fetch marketplace lookups are reads.
Across retries and async work
Keep the same requestId when you retry a failed call or hand work to a queue, so support can see one thread instead of three unrelated IDs.
MCP, Ask, and typed REST all return it on the envelope. Browser free tools may not surface it in the UI. Product posture: /reliability.
FAQ
Is requestId on MCP and Ask too?
Yes. Same envelope. Ask responses include it for the call; nested lookup metadata follows the routed operation's shape.
Where do I read more?
/unified-schema for the envelope, /reliability for support posture, /docs/errors for error shapes.
Do free tools expose requestId?
Browser free tools may not surface it in the UI. API and MCP responses do.