Skip to content

Certificates

Some APIs only answer when you present a certificate. Set it per environment in SSLConfiguration, the same setting JetBrains IDEs use, or in the Environments tab under Client certificate (mTLS), which saves it in your private file.

http-client.env.json
{
"dev": {
"SSLConfiguration": {
"clientCertificate": "./certs/me.pfx",
"hasCertificatePassphrase": true
}
}
}
http-client.env.json.user
{
"dev": {
"SSLConfiguration": {
"certificatePassphrase": "…"
}
}
}
  • clientCertificate is a .pfx or .p12 file, or a PEM certificate with clientCertificateKey for its key (unless the key is in the same file). Paths are relative to the env file.
  • With hasCertificatePassphrase, Reqjet asks for the passphrase once per session, or reads certificatePassphrase from the private file. That setting is Reqjet’s own; JetBrains IDEs ignore it and ask.
  • The certificate is also used for OAuth token requests, WebSockets and server-sent events.
  • Copy as cURL adds --cert, without the passphrase.

On the command line, the passphrase comes from the private file, or is asked for on the terminal.

By default, Reqjet checks the server’s certificate, as a browser does. For a development server with a self-signed certificate, turn the check off for that environment:

http-client.env.json
{
"local": {
"baseUrl": "https://localhost:5001",
"SSLConfiguration": {
"verifyHostCertificate": false
}
}
}

Only turn it off for servers you control: without the check, anyone between you and the server could read and change the traffic.

The Timing tab on a response shows the server’s certificate: its names, issuer and valid dates, with a warning when it expires within a month.