Social docs
API reference

Social API.

Communities, posts, ranked feeds, stories, polls, moderation — every endpoint generated from the live OpenAPI spec.

Social is keyed on community_id for the customer-backend lane. Each end-user of your product is projected as an actor viaPOST /v1/communities/{community_id}/actors. All subsequent posts, edges, comments, votes, and views reference the actor by their actor.id — the UUID Social returned at upsert time. Your customer-supplied external_id is only the upsert key and the input to the GET .../actors/by-external/{external_id} lookup; every other parameter named actor_id takes the UUID.

The customer-backend lane authenticates with your workspace API key (pcft_live_*) as a bearer token. The admin lane under /v1/workspaces/{workspace_id}/... accepts a API key bearer, a PlatformUser bearer (console JWT), or the platform session cookie — the same pcft_live_* key you use below also works there, provided its policy grants the workspace-scoped permissions each route names.

Base URL

https://api.social.productcraft.co

Auth

Authorization: Bearer …

Spec version

OpenAPI 3.0.0 · v0.1.0

Conversations

Direct messages: one-to-one and group conversations, their members and messages.


Edges

The social graph: follow, mute, block and restrict between members, follow requests for private members, and the lists that read them.


Post-Reactions

Reactions (like and the other reaction types) on posts.


Webhooks

Webhook endpoints that receive post, comment, follow, moderation, message and media events, their delivery log and replays, at the workspace or for one community. The legacy per-community webhook routes are deprecated.


Workspace lane

Admin API

Community CRUD, settings, the moderation queue and audit log, conversation moderation and analytics: the workspace-scoped endpoints the console is built on. Admin API reference →