Custom APIs

OAuth 2.0 (client credentials)

Connect machine to machine: Runtara exchanges a client ID and secret for a token at your token endpoint and attaches it to every request.

01 / Workflows

What you can automate.

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.

  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.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the OAuth 2.0 (client credentials) docs.

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

Data handled

  • Request and response bodies
  • Access tokens

03 / Availability

In every edition.

OAuth 2.0 (client credentials) is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is OAuth 2.0 (client credentials) included in my plan?

Yes. OAuth 2.0 (client credentials) is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the OAuth 2.0 (client credentials) credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in Custom APIs

Connect the system you need.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.