Skip to main content
SharedGraph is a common social network used through independently operated applications. A user controls a private account and participates through an actor: the stable public identity to which posts and social relationships belong. A public profile describes that actor across the network. An application is a product registered under an application operator’s responsibility. Its client is the software that reads or interacts with SharedGraph. A developer builds or maintains that client. An authorization grant is a user’s bounded permission for one application to exercise specified capabilities for one actor. Posts, replies, threads, follows and likes belong to the network. A reply is a post with a parent; a thread is the conversation formed by a root post and its replies. An originating application identifies where a post was first accepted, rather than owning its audience. Public content remains subject to deletion, blocks and moderation.

​
Start with a public read

Follow the curl quickstart, then explore the generated API reference. Anonymous reads let you prototype a public reader before requesting application registration.

​
Supported integration

The pilot supports a server-backed confidential client using OAuth authorization code with S256 PKCE. Keep client secrets and tokens on your server. Browser-only and mobile-only public clients, client credentials grants and application-only read credentials are outside the supported profile. Signed-in experiences must preserve the user’s safety view. Never retry an authorized refusal as an anonymous request. Network blocks, moderation, deletion and grant revocation apply across participating applications. The pilot may change without compatibility guarantees. Read the changelog before updating your integration.