Authentication

Authentication Overview

Choose the right OAuth 2.0 flow for your application.

Choosing an Authentication Method

Rightbrain utilizes the industry-standard OAuth 2.0 framework for authentication and authorization. To interact with the Rightbrain API, your application must first obtain an access token using one of the supported OAuth 2.0 grant types (flows). The access token is then included in the Authorization header of your API requests.

The appropriate grant type depends on the nature of your application. Select the grant type that best fits your application’s architecture and security requirements, then follow the detailed steps on the corresponding page.

Client Credentials Grant

Best for: Machine-to-machine (M2M) applications like backend services, daemons, or scripts acting on their own behalf.


  • Credentials: Client ID, Client Secret
  • User Interaction: None
  • Refreshable: No
Authorization Code Grant

Best for: Traditional server-side web applications where a user logs in and the application can securely store a Client Secret.


  • Credentials: Client ID, Client Secret, Redirect URI
  • User Interaction: Yes (login & consent)
  • Refreshable: Yes (requires offline_access scope)
Authorization Code + PKCE

Best for: Public clients (SPAs, mobile/desktop apps) that cannot securely store a Client Secret. Recommended for all clients.


  • Credentials: Client ID, Redirect URI
  • User Interaction: Yes (login & consent)
  • Refreshable: Yes (requires offline_access scope)