Being You

Developer platform

Build integrations and let people Continue with Being You using OAuth 2.1 authorization code + PKCE.

Create an application

Available scopes
  • profile — Basic Being You identity: account id and username
  • email — Verified account email address
  • social.read — Read the member's own posts
  • social.write — Publish text posts for the member
  • professional.read — Read professional profile and project portfolio
  • circles.read — Read the member's Circle memberships
  • offline_access — Issue rotating refresh tokens for long-lived integrations

Your applications

Loading applications…

Sign in with Being You

Use OAuth 2.1 authorization code with PKCE S256. Redirect URIs are exact-match only. Public/mobile clients do not receive a secret; confidential backend apps authenticate at the token endpoint.

  1. Generate a cryptographically random 43–128 character code_verifier and BASE64URL(SHA256(verifier)) code_challenge.
  2. GET /oauth/authorize?response_type=code&client_id=…&redirect_uri=…&scope=profile%20email&state=…&code_challenge=…&code_challenge_method=S256
  3. Exchange the returned one-time code at POST /oauth/token using application/x-www-form-urlencoded.
  4. Call GET /api/v1/me with Authorization: Bearer <access_token>.

Developer endpoints

  • /.well-known/oauth-authorization-server discovery
  • /oauth/token code exchange / refresh-token rotation
  • /oauth/revoke token revocation
  • /oauth/introspect confidential-client token introspection
  • /api/v1/me identity
  • /api/v1/me/professional professional profile
  • /api/v1/me/projects portfolio
  • /api/v1/me/posts own posts
  • POST /api/v1/posts publish text post
  • /api/v1/me/circles Circle memberships

No OAuth scope grants access to passwords, private messages, wallet/payment data or staff/admin operations. Access and refresh tokens are opaque and stored hashed at rest.