Skip to main content

Content visibility

The DFOS API follows the same visibility choices that spaces and authors make in DFOS. It cannot be used to bypass them.

Spaces​

Only spaces that have enabled a public profile appear in the API. A private space and a space that does not exist both return 404 Not Found.

Public space responses contain only public profile and site information. They do not expose membership, private activity, or viewer-specific state.

Posts​

Only posts shared to everyone can appear. A post may be public because it was shared to everyone directly or because it was published in a public topic. Posts that require an account, membership, or other access do not appear.

When a post contains a fold marker (<!--fold-->), the API returns only the content above the fold. Inline media that appears only below the fold is also omitted, and the response sets folded to true.

Media referenced by a readable post comes back inline. Public images resolve to a permanent public CDN URL; private media (audio, video, and file attachments) comes back as a time-limited signed URL that stops working after its urlExpiresAt. Either way, you only ever receive media the post itself makes readable — nothing below the fold, and nothing from a post you can't read. See Media URLs for the two URL classes.

These rules are identical for list and single-post endpoints: if a post cannot appear in a space's public feed, fetching it directly returns 404 Not Found.