Organization API: Customer Portal: Community

Part of Customer Portal.

GET /api/v1/orgs/{org_slug}/portal/community/forum/me

The signed-in member as the forum chrome sees them: handle, role, unread followed threads, and the open report count for staff.

Also the one request a member who only reads makes with their token, so ensure_profile stamping them present here is what keeps Active … ago honest for somebody who never posts; the storefront asks again when its copy is a few minutes old.

POST /api/v1/orgs/{org_slug}/portal/community/forum/moderation/members/{handle}/role

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/forum/moderation/members/{handle}/suspend

application/json (required)

GET /api/v1/orgs/{org_slug}/portal/community/forum/moderation/reports

POST /api/v1/orgs/{org_slug}/portal/community/forum/moderation/reports/{report_id}/resolve

Close a report, optionally acting on what it pointed at.

The action and the closing are one request, so the queue cannot end up with a removed post and a report still open against it. Nor can it end up the other way round, which is worse: a dismissed report and content nobody looked at.

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/forum/moderation/threads/{thread_id}/flags

Pin, lock, move or mark a thread as a duplicate.

The duplicate marker is the one that matters for search: it takes the newer thread out of the index and leaves the older one holding the ranking, which is the opposite of what happens if you simply delete the repost.

application/json (required)

PUT /api/v1/orgs/{org_slug}/portal/community/forum/posts/{post_id}

application/json (required)

DELETE /api/v1/orgs/{org_slug}/portal/community/forum/posts/{post_id}

POST /api/v1/orgs/{org_slug}/portal/community/forum/posts/{post_id}/react

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/forum/posts/{post_id}/vote

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/forum/reports

application/json (required)

GET /api/v1/orgs/{org_slug}/portal/community/forum/subscriptions

Threads the member follows, with how many posts they have not seen.

POST /api/v1/orgs/{org_slug}/portal/community/forum/subscriptions/read

POST /api/v1/orgs/{org_slug}/portal/community/forum/threads

application/json (required)

PUT /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}

application/json (required)

DELETE /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}

POST /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/bump

POST /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/posts

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/solution

Accept a reply as the answer.

The reference forum has no such thing, which is why its question boards are thousands of pages that end without one. An accepted answer is the single strongest signal in the relevance score, and the only one that promotes a thread into the assistant-facing export.

DELETE /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/solution

POST /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/subscription

DELETE /api/v1/orgs/{org_slug}/portal/community/forum/threads/{thread_id}/subscription

Stop following, idempotently. The toggle is wrong for a list of Unfollow buttons, where a double click would follow again.

GET /api/v1/orgs/{org_slug}/portal/community/guides/articles

POST /api/v1/orgs/{org_slug}/portal/community/guides/articles

application/json (required)

GET /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}

PUT /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}

application/json (required)

DELETE /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}

The author removing their own guide, whatever state it is in.

A hard delete, on purpose: the author is withdrawing something they wrote, and a row kept around "archived" would still be theirs to find in the library and staff's to stumble over in the queue. Revisions, comments, votes, reports and notifications go with it. The rows are removed in dependency order rather than left to the cascades, because the two article→revision keys were added best-effort and may not exist on an older database.

GET /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}/diff

POST /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}/proposal/withdraw

POST /api/v1/orgs/{org_slug}/portal/community/guides/articles/{article_id}/propose

application/json (required)

GET /api/v1/orgs/{org_slug}/portal/community/guides/moderation

POST /api/v1/orgs/{org_slug}/portal/community/guides/moderation/articles/{article_id}/approve

POST /api/v1/orgs/{org_slug}/portal/community/guides/moderation/articles/{article_id}/reject

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/guides/moderation/comments/{comment_id}/approve

POST /api/v1/orgs/{org_slug}/portal/community/guides/moderation/comments/{comment_id}/reject

application/json (required)

POST /api/v1/orgs/{org_slug}/portal/community/guides/moderation/reports/{report_id}/resolve

Close a report. Without this the queue only ever grew.

GET /api/v1/orgs/{org_slug}/portal/community/guides/notifications

POST /api/v1/orgs/{org_slug}/portal/community/guides/notifications/{notification_id}/read

POST /api/v1/orgs/{org_slug}/portal/community/members/{handle}/wall

application/json (required)

GET /api/v1/orgs/{org_slug}/portal/community/profile

PUT /api/v1/orgs/{org_slug}/portal/community/profile

application/json (required)

DELETE /api/v1/orgs/{org_slug}/portal/community/wall/comments/{comment_id}

DELETE /api/v1/orgs/{org_slug}/portal/community/wall/{wall_post_id}

POST /api/v1/orgs/{org_slug}/portal/community/wall/{wall_post_id}/comments

application/json (required)