Private Endpoint Docs

Private docs cover live routes that are not meant to be treated as direct integration surfaces.

These are usually:

  • first-party SSO bridge endpoints
  • relay-backed token issue or exchange helpers
  • retained legacy handlers

Important nuance:

  • private here does not mean unreachable on the network
  • it means the route is not part of the supported direct API contract
  • callers should normally go through the first-party surface that owns the flow

Current Private Families

Current Private Route Roots

  • /auth/user/*
  • /auth/member/*
  • /auth/signup
  • /oauth/client_credentials/issue

Current Security Stance

The live auth bridge family is no longer a public auth surface.

As of the current route state:

  • the live auth bridge endpoints require first-party bridge context
  • the auth and member-auth token-mint and token-exchange routes require a single-use dead-drop relay
  • these routes should be treated as SSO backing APIs, not as third-party login or token endpoints
1