Custom APIs

HTTP bearer token

Call any HTTPS API that accepts a bearer token, such as a personal access token or a long-lived API token, without putting it in your workflows.

01 / Workflows

What you can automate.

The bearer token connection stores a token and the API's HTTPS base URL. HTTP steps send the token in the Authorization header and can only call URLs under that base URL.

  1. Call a SaaS API with a personal access token.
  2. Reach an internal service that issues long-lived API tokens.
  3. Post results to a webhook endpoint that expects a bearer token.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the HTTP bearer token docs.

Capabilities

  • Token sent as an Authorization: Bearer header
  • Requests pinned to one HTTPS base URL
  • Credentials kept out of workflow definitions

Data handled

  • Request and response bodies
  • Response status and headers

03 / Availability

In every edition.

HTTP bearer token 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 HTTP bearer token included in my plan?

Yes. HTTP bearer token is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the HTTP bearer token 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.