DFOS API

The DFOS API provides HTTP access to public spaces, posts, pages, events, products, and user profiles at https://api.dfos.com/v1/. Most of it is anonymous: no API key, no access token, no DFOS account. Every anonymous response is viewer-independent — the same for any caller — and scoped to content that spaces and authors have made public.

What needs a credential

Apart from key proof, whose signed envelope is its own authentication, the rest needs a credential a user issued through Sign in with DFOS, and serves what that user can see to the app they granted it to: GET /v1/profile, the membership routes, GET /v1/credential, GET /v1/feed, the post comments route, and the write routes. The two space post routes sit in between: they work anonymously, and a covering credential turns the public feed into the one the granting user sees (optional authentication).

Resources

Start with the quickstart, then Conventions for authentication, pagination, identifiers, and errors. The resource pages — Spaces, Pages, Posts, Topics, Events, Products, Users, Profile, Memberships, Credential, Key proof, and protocol discovery — document what each field means and what to store.

Guides

Show your space's posts on your own site, Verify a post, Gate on membership, and Post a comment.

The contract

Content visibility, rate limits and caching, and the compatibility contract. Try every endpoint in the interactive reference, or read the raw spec as JSON or YAML.