Sign a JWT Bearer token#

JWT Bearer builds a signed token for you. You give it a payload and a key. The app signs a JSON Web Token each time you send, then attaches it as an Authorization header. This method suits APIs that accept a self-signed JWT rather than one issued by a login flow.

Select a signing algorithm#

The Algorithm dropdown sets how the app signs the token. The HMAC options (HS256, HS384, HS512) use a single shared secret. The RSA options (RS256, RS384, RS512) and the ECDSA options (ES256, ES384) use a private key.

Your choice changes the field below. For HMAC you fill in a Secret, a shared string that you can also supply as a {{variable}}. For RSA or ECDSA you paste a Private key in PEM form. The key starts with a -----BEGIN PRIVATE KEY----- line.

Set the payload and prefix#

Three fields shape the token the app sends:

• Payload (JSON): holds the token's claims, for example a subject and a scope. Write it as a JSON object.
• Add exp claim: adds an exp claim set to one hour ahead. Default on.
• Header prefix: sets the word before the token in the Authorization header. Default Bearer, which gives Authorization: Bearer <jwt>.

Leave Add exp claim on so the token does not linger. Set it to use the payload as-is when you want to manage expiry yourself. Change the header prefix only if your API expects a different word.

The app signs the token every time you send, so an updated payload or key takes effect on the next request.