Developers
V1SocialModeration

Non-impersonating moderator: pending profile or club text

GET
/v1/social/moderation

Authorization

bearer
AuthorizationBearer <token>

In: header

Query Parameters

cursor?string
Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid
limit?integer
Range1 <= value <= 50
Default20
targetType*string

Value in

  • "profile"
  • "club"

Response Body

application/json

curl -X GET "https://example.com/v1/social/moderation?targetType=profile"
{  "items": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "targetType": "profile",      "revision": 1,      "submittedAt": "2019-08-24T14:15:22Z",      "text": {        "alias": "string",        "handle": "string",        "title": "string",        "summary": "string"      }    }  ],  "nextCursor": "53a4a333-2825-45a4-80d2-5f430d088f36"}

Choose whether eligible viewers may browse your accepted connections PUT

Separate, versioned consent; defaults off. Does not enable discovery or public visibility. A pending profile can still change this choice. Other people's connections require both parties' consent and profile access; your own connections remain available to you.

Approve/reject an exact text revision with an append-only decision POST

Requires a Better Auth session with a live platform admin role and no impersonation. Moderators cannot approve their own content. A stale revision is rejected.