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

Custom API

OAuth 2.0 (client credentials)

You set the token URL, the client ID and secret, optional scopes, and the API base URL, all over HTTPS. Runtara requests the token itself, with optional audience and resource parameters for providers that need them, so no one has to sign in.

For plans and availability, see the OAuth 2.0 (client credentials) integration.

Common use cases

  1. Call an API protected by an identity provider such as Auth0 or Keycloak.
  2. Connect service to service without a user account.
  3. Reach a partner API that issues client credentials to integrators.

Capabilities

  • Token minted from your own token endpoint
  • Optional scope, audience and resource parameters
  • Client secret sent in the form body or a Basic header
  • Requests pinned to one HTTPS base URL

Connection types

http_oauth2_client_credentials

Data handled

  • Request and response bodies
  • Access tokens