Custom APIs

Mutual TLS (client certificate)

Call HTTPS APIs that identify callers by a client certificate rather than, or as well as, a key, including servers on a private certificate authority.

01 / Workflows

What you can automate.

The mutual TLS connection stores a PEM client certificate chain and its private key, the API's HTTPS base URL, and optionally a CA bundle for servers with a private trust chain. HTTP steps present the certificate on every request.

  1. Reach an enterprise API gateway that requires client certificates.
  2. Connect to a partner system on a private certificate authority.
  3. Add certificate authentication on top of an API key.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the Mutual TLS (client certificate) docs.

Capabilities

  • PEM certificate chain and unencrypted private key (PKCS#8, RSA or EC)
  • Optional CA bundle for private server certificates
  • Requests pinned to one HTTPS base URL

Data handled

  • Request and response bodies
  • Client certificate and private key

03 / Availability

In every edition.

Mutual TLS (client certificate) 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 Mutual TLS (client certificate) included in my plan?

Yes. Mutual TLS (client certificate) is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the Mutual TLS (client certificate) 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.