OpenVibe.Community API
Generated at from
openvibe-contracts v0.53.0 and
openvibe-sdk v0.11.0.
Server https://openvibe.community. 36 routes performing 10 capabilities. OpenAPI 3.1 document.
POST /api/pastes
Create a paste (text or screenshot).
- Capabilities
- community.paste.create
- Visibility
- public
- Request body
application/jsoncommunity.paste-create-request@1- Response
application/jsoncommunity.paste-create-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.create</strong> (public): Create a paste (text or screenshot). A service token creates it for the acting subject named in X-OV-Subject, or as origin "ai" for derived pastes (roadmap 33).</p> <p>Route note: Community</p>PUT /api/pastes/{slug}
Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject).
- Capabilities
- community.paste.write
- Visibility
- first-party
- Parameters
slug(path, required)
- Request body
application/jsoncommunity.paste-write-request@1- Response
application/jsoncommunity.paste-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.write</strong> (first-party): Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject). Ownership is checked by Community, never by the caller.</p>DELETE /api/pastes/{slug}
Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject).
- Capabilities
- community.paste.write
- Visibility
- first-party
- Parameters
slug(path, required)
- Input
- community.paste-write-request@1
- Response
application/jsoncommunity.paste-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.write</strong> (first-party): Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject). Ownership is checked by Community, never by the caller.</p>POST /api/pastes/{slug}/{fork,like,copy,comments}
Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject).
- Capabilities
- community.paste.write
- Visibility
- first-party
- Parameters
slug(path, required)fork,like,copy,comments(path, required)
- Request body
application/jsoncommunity.paste-write-request@1- Response
application/jsoncommunity.paste-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.write</strong> (first-party): Edit, delete, fork, like, copy and comment on pastes as the acting subject (X-OV-Subject). Ownership is checked by Community, never by the caller.</p>POST /api/pastes/{slug}/censor
Staff moderation of any paste or comment (censor, delete, bulk).
- Capabilities
- community.paste.moderate
- Visibility
- internal
- Parameters
slug(path, required)
- Request body
application/jsoncommunity.paste-moderate-request@1- Response
application/jsoncommunity.paste-moderate-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.moderate</strong> (internal): Staff moderation of any paste or comment (censor, delete, bulk). The caller vouches that the acting subject is staff.</p>DELETE /api/pastes/{slug}/comments/{id}
Staff moderation of any paste or comment (censor, delete, bulk).
- Capabilities
- community.paste.moderate
- Visibility
- internal
- Parameters
slug(path, required)id(path, required)
- Input
- community.paste-moderate-request@1
- Response
application/jsoncommunity.paste-moderate-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.moderate</strong> (internal): Staff moderation of any paste or comment (censor, delete, bulk). The caller vouches that the acting subject is staff.</p>POST /api/pastes/bulk
Staff moderation of any paste or comment (censor, delete, bulk).
- Capabilities
- community.paste.moderate
- Visibility
- internal
- Request body
application/jsoncommunity.paste-moderate-request@1- Response
application/jsoncommunity.paste-moderate-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.paste.moderate</strong> (internal): Staff moderation of any paste or comment (censor, delete, bulk). The caller vouches that the acting subject is staff.</p>DELETE /api/v1/comments/{commentId}
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate, community.comment.write
- Visibility
- internal, first-party
- Parameters
commentId(path, required)
- Input
- one of community.moderation-request@1, community.comment-write-request@1
- Response
- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p> <p><strong>community.comment.write</strong> (first-party): Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Subject), or comment as origin "ai" (never attributed to a person, roadmap 33). Ownership and limits are checked by Community.</p>POST /api/v1/comments/{commentId}/votes
Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Sub
- Capabilities
- community.comment.write
- Visibility
- first-party
- Parameters
commentId(path, required)
- Request body
application/jsoncommunity.comment-write-request@1- Response
application/jsoncommunity.comment-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.write</strong> (first-party): Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Subject), or comment as origin "ai" (never attributed to a person, roadmap 33). Ownership and limits are checked by Community.</p>GET /api/v1/comments/threads/{id}
Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Sub
- Capabilities
- community.comment.write
- Visibility
- first-party
- Parameters
id(path, required)
- Input
- community.comment-write-request@1
- Response
application/jsoncommunity.comment-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.write</strong> (first-party): Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Subject), or comment as origin "ai" (never attributed to a person, roadmap 33). Ownership and limits are checked by Community.</p>POST /api/v1/comments/threads/{id}/comments
Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Sub
- Capabilities
- community.comment.write
- Visibility
- first-party
- Parameters
id(path, required)
- Request body
application/jsoncommunity.comment-write-request@1- Response
application/jsoncommunity.comment-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.write</strong> (first-party): Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Subject), or comment as origin "ai" (never attributed to a person, roadmap 33). Ownership and limits are checked by Community.</p>PUT /api/v1/comments/threads/{id}/visibility
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate
- Visibility
- internal
- Parameters
id(path, required)
- Request body
application/jsoncommunity.moderation-request@1- Response
application/jsoncommunity.moderation-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p>POST /api/v1/comments/threads/resolve
Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Sub
- Capabilities
- community.comment.write
- Visibility
- first-party
- Request body
application/jsoncommunity.comment-write-request@1- Response
application/jsoncommunity.comment-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.write</strong> (first-party): Typed comment threads as a service: resolve the thread of any EntityRef (browsers are limited to an allowlist of types), and comment, vote and delete one's own comments as the acting subject (X-OV-Subject), or comment as origin "ai" (never attributed to a person, roadmap 33). Ownership and limits are checked by Community.</p>PUT /api/v1/posts/{id}
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate, community.post.create
- Visibility
- internal, public
- Parameters
id(path, required)
- Request body
- Response
- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p> <p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>DELETE /api/v1/posts/{id}
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate, community.post.create
- Visibility
- internal, public
- Parameters
id(path, required)
- Input
- one of community.moderation-request@1, community.post-write-request@1
- Response
- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p> <p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>GET /api/v1/pulse
Read the network's public activity feed (Pulse): entity reference, title, URL and origin (user, ai or system), newest first with a cursor.
- Capabilities
- community.pulse.read
- Visibility
- public
- Response
application/jsoncommunity.pulse-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.pulse.read</strong> (public): Read the network's public activity feed (Pulse): entity reference, title, URL and origin (user, ai or system), newest first with a cursor. Only public items are ever stored. Served to anyone (CORS allow-list for browsers). Live's /api/home/pulse is a different, Live-only feed.</p>POST /api/v1/pulse/items
Publish public activity of the calling service's own entities to Pulse (EntityRef + title + url + origin user|ai|system + occurred_at), or retract it.
- Capabilities
- community.pulse.write
- Visibility
- first-party
- Request body
application/jsoncommunity.pulse-write-request@1- Response
application/jsoncommunity.pulse-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.pulse.write</strong> (first-party): Publish public activity of the calling service's own entities to Pulse (EntityRef + title + url + origin user|ai|system + occurred_at), or retract it. Only visibility public is accepted; the ref's service must be the caller's. Provenance is kept: the first record's origin, actor (X-OV-Subject, never for ai/system) and time stand.</p>DELETE /api/v1/pulse/items/{service}/{type}/{id}
Publish public activity of the calling service's own entities to Pulse (EntityRef + title + url + origin user|ai|system + occurred_at), or retract it.
- Capabilities
- community.pulse.write
- Visibility
- first-party
- Parameters
service(path, required)type(path, required)id(path, required)
- Input
- community.pulse-write-request@1
- Response
application/jsoncommunity.pulse-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.pulse.write</strong> (first-party): Publish public activity of the calling service's own entities to Pulse (EntityRef + title + url + origin user|ai|system + occurred_at), or retract it. Only visibility public is accepted; the ref's service must be the caller's. Provenance is kept: the first record's origin, actor (X-OV-Subject, never for ai/system) and time stand.</p>GET /api/v1/relay/*
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate
- Visibility
- internal
- Input
- community.moderation-request@1
- Response
application/jsoncommunity.moderation-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p>POST /api/v1/relay/*
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate
- Visibility
- internal
- Request body
application/jsoncommunity.moderation-request@1- Response
application/jsoncommunity.moderation-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p>PUT /api/v1/relay/*
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate
- Visibility
- internal
- Request body
application/jsoncommunity.moderation-request@1- Response
application/jsoncommunity.moderation-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p>GET /api/v1/spaces
List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*).
- Capabilities
- community.space.read
- Visibility
- public
- Response
application/jsoncommunity.space-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.space.read</strong> (public): List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*). Anonymous callers see public spaces, signed-in people also members spaces, moderators also staff spaces; members-only (VIP) spaces are flagged. Served to anyone; Community checks space visibility itself.</p>GET /api/v1/spaces/{space}
List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*).
- Capabilities
- community.space.read
- Visibility
- public
- Parameters
space(path, required)
- Response
application/jsoncommunity.space-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.space.read</strong> (public): List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*). Anonymous callers see public spaces, signed-in people also members spaces, moderators also staff spaces; members-only (VIP) spaces are flagged. Served to anyone; Community checks space visibility itself.</p>GET /api/v1/spaces/{space}/threads
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Parameters
space(path, required)
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.thread.read</strong> (public): Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds. Community checks space visibility and the VIP gate (403 vip.members_only). Creating threads and replies stays community.post.create.</p>POST /api/v1/spaces/{space}/threads
Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI
- Capabilities
- community.post.create
- Visibility
- public
- Parameters
space(path, required)
- Request body
application/jsoncommunity.post-write-request@1- Response
application/jsoncommunity.post-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>GET /api/v1/spaces/{space}/threads/{slug}
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Parameters
space(path, required)slug(path, required)
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.thread.read</strong> (public): Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds. Community checks space visibility and the VIP gate (403 vip.members_only). Creating threads and replies stays community.post.create.</p>DELETE /api/v1/spaces/{space}/threads/{slug}
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate, community.post.create
- Visibility
- internal, public
- Parameters
space(path, required)slug(path, required)
- Input
- one of community.moderation-request@1, community.post-write-request@1
- Response
- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p> <p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>POST /api/v1/spaces/{space}/threads/{slug}/posts
Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI
- Capabilities
- community.post.create
- Visibility
- public
- Parameters
space(path, required)slug(path, required)
- Request body
application/jsoncommunity.post-write-request@1- Response
application/jsoncommunity.post-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>PUT /api/v1/spaces/{space}/threads/{slug}/state
Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g.
- Capabilities
- community.comment.moderate
- Visibility
- internal
- Parameters
space(path, required)slug(path, required)
- Request body
application/jsoncommunity.moderation-request@1- Response
application/jsoncommunity.moderation-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.comment.moderate</strong> (internal): Moderation of discussions: set a comment thread's visibility (public, hidden, locked — e.g. when the owner service hides the entity), delete any comment or forum post, pin and lock forum threads, read hidden threads, administer the Discord relay. Acting as itself (no X-OV-Subject) the service is the moderator; acting for a person it must vouch with X-OV-Staff: 1 that the person is staff.</p>POST /api/v1/spaces/{space}/threads/{slug}/votes
Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI
- Capabilities
- community.post.create
- Visibility
- public
- Parameters
space(path, required)slug(path, required)
- Request body
application/jsoncommunity.post-write-request@1- Response
application/jsoncommunity.post-write-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.post.create</strong> (public): Forum writes as a service: create threads and replies in a space, vote on threads, and edit or delete one's own posts, as the acting subject (X-OV-Subject) or as origin "ai" (no author, labelled as AI). Space visibility (public, members, staff), locks and limits are checked by Community.</p>GET /pulse
Read the network's public activity feed (Pulse): entity reference, title, URL and origin (user, ai or system), newest first with a cursor.
- Capabilities
- community.pulse.read
- Visibility
- public
- Response
application/jsoncommunity.pulse-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.pulse.read</strong> (public): Read the network's public activity feed (Pulse): entity reference, title, URL and origin (user, ai or system), newest first with a cursor. Only public items are ever stored. Served to anyone (CORS allow-list for browsers). Live's /api/home/pulse is a different, Live-only feed.</p>GET /s
List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*).
- Capabilities
- community.space.read
- Visibility
- public
- Response
application/jsoncommunity.space-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.space.read</strong> (public): List the spaces the caller can open and read one space's metadata (roadmap §30.2 community.space.*). Anonymous callers see public spaces, signed-in people also members spaces, moderators also staff spaces; members-only (VIP) spaces are flagged. Served to anyone; Community checks space visibility itself.</p>GET /s/{space}
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Parameters
space(path, required)
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.thread.read</strong> (public): Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds. Community checks space visibility and the VIP gate (403 vip.members_only). Creating threads and replies stays community.post.create.</p>GET /s/{space}/feed.xml
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Parameters
space(path, required)
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.thread.read</strong> (public): Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds. Community checks space visibility and the VIP gate (403 vip.members_only). Creating threads and replies stays community.post.create.</p>GET /s/{space}/t/{slug}
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Parameters
space(path, required)slug(path, required)
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)
Description
<p><strong>community.thread.read</strong> (public): Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds. Community checks space visibility and the VIP gate (403 vip.members_only). Creating threads and replies stays community.post.create.</p>GET /s/feed.xml
Read a space's threads (hot, new or top, paged) and one thread with its posts, plus the RSS feeds.
- Capabilities
- community.thread.read
- Visibility
- public
- Response
application/jsoncommunity.thread-read-result@1- Errors
- errors.problem@1 (application/problem+json)