Sign-in
Sign-in built in
OAuth 2.0, Digest, AWS Signature V4, Windows NTLM and Negotiate, client certificates and proxies, set up in the same environment files JetBrains IDEs use and VS Code REST Client's header syntax.
OAuth 2.0
Tokens fetched, cached and refreshed
Profiles live in the environment files. A request uses a profile's token as {{$auth.token("id")}}; Reqjet gets it when the request is sent, keeps it for the session and refreshes it when it expires.
- Client credentials, password and authorization code (opening your browser, with PKCE).
- Secrets in the private file: settings there override the team file's one by one.
- The command line gets tokens the same way.
{ "dev": {
"Security": { "Auth": { "my-api": {
"Type": "OAuth2",
"Grant Type": "Client Credentials",
"Token URL": "https://login.example.com/token",
"Client ID": "reqjet",
"Scope": "orders:read"
} } } } }
── orders.http ─────────────────────────
GET {{baseUrl}}/orders
Authorization: Bearer {{$auth.token("my-api")}}
Digest, AWS and Windows
Written as the Authorization header (Digest, AWS, NTLM, Negotiate) and worked out when the request is sent, so the files work in VS Code REST Client too.
Client certificates
For APIs that only answer to a certificate (mTLS): a .pfx or PEM per environment, with the passphrase asked for once or kept in the private file.
Corporate proxies
The system proxy by default, or a manual one with a bypass list. A proxy that asks for a sign-in gets your Windows credentials.
More features
There's more where that came from
Try it on your own requests
Free for Windows, macOS and Linux, and it opens the .http files you already have.