OAuth 2.0 (authorization code)Reference for the OAuth 2.0 (authorization code) connection in Runtara: what it is used for, its capabilities, connection types and the data it handles.AgentsdocsAgentsdocsagentscustom api

Custom API

OAuth 2.0 (authorization code)

You set the authorization and token URLs, the client ID and secret, the scopes, and the API base URL, all over HTTPS. Signing in captures the token, and Runtara refreshes it as needed, including with providers that rotate refresh tokens. PKCE is on by default.

For plans and availability, see the OAuth 2.0 (authorization code) integration.

Common use cases

  1. Connect to a SaaS API that only offers OAuth sign-in.
  2. Act on behalf of a specific user account in another system.
  3. Replace a shared password with a revocable, scoped token.

Capabilities

  • Interactive sign-in with PKCE
  • Tokens refreshed automatically, including rotating refresh tokens
  • Client secret sent in the form body or a Basic header
  • Optional token revocation when the connection is deleted
  • Requests pinned to one HTTPS base URL

Connection types

http_oauth2_authorization_code

Data handled

  • Request and response bodies
  • Access and refresh tokens