Bettermode · Authentication Profile
Bettermode Authentication
Authentication
Bettermode's GraphQL API is authenticated with bearer access tokens passed on the Authorization header. Two token classes are documented: App Access Tokens (for installed apps acting server-to-server) and Member Access Tokens (acting as a specific community member). Guest tokens grant limited unauthenticated read access. There are no API keys or scopes in the classic OAuth sense; an app's reach is bounded by the communities it is installed on and the permissions granted at install time.
Bettermode secures its APIs with http across 3 declared security schemes, as derived from its OpenAPI definitions.
CommunityCustomer CommunityCommunity PlatformCustomer EngagementCustomer SuccessGraphQLWebhookNo-CodeSoftware-as-a-ServiceDevelopers
Methods: http
Schemes: 3
OAuth flows:
API key in:
Security Schemes
AppAccessToken http
MemberAccessToken http
GuestToken http
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.