Skip to content
Scope an integration

Glossary

What is OAuth 2.0?

OAuth 2.0 is an authorization framework that lets an application access another service's API on a user's behalf without handling the user's password.

OAuth 2.0 is the standard authorization framework (RFC 6749) behind “Connect to…” buttons. Instead of sharing a password, the user approves specific permissions, called scopes, and the application receives an access token to call the API on their behalf. Most modern HRIS, CRM and LMS APIs use OAuth 2.0 for third-party integrations.

How does it work?

  1. The application redirects the user to the provider’s authorization page with requested scopes.
  2. The user signs in and approves access.
  3. The provider redirects back with an authorization code.
  4. The application exchanges the code for an access token, and usually a refresh token, then calls the API.
  5. When the access token expires, it uses the refresh token to get a new one.

OAuth 2.0 handles authorization, not authentication. If an application needs to know who the user is, it typically adds OpenID Connect on top, which returns an ID token alongside the access token.

Where it shows up in integrations

  • Marketplace connectors Each customer connects their own BambooHR or CRM account through OAuth.
  • Server-to-server The client credentials grant is used when no end user is involved.
  • Scoped access Requesting only the scopes an integration needs simplifies security reviews.

Common pitfalls

  • Storing tokens unencrypted or logging them.
  • Not handling refresh-token expiry or revocation, so integrations fail silently.
  • Requesting more scopes than the integration needs.
  • Skipping PKCE and state checks in the authorization code flow.