Signing a JWT in HTML: HS256 Example

HTML JWT generator quickstart

Create a token with your public API key in the sub claim, a near-term Unix timestamp in exp, and an HS256 signature made with your private API key.

Sapling JWTs use HS256 with a sub claim containing your public API key and an exp claim containing a Unix timestamp. The examples use a one-hour lifetime; shorten it further when your application can refresh tokens easily.

HTML HS256 · sub + exp

Never sign a JWT in browser code. Have your backend return a short-lived token without exposing the private API key.

<script src="https://sapling.ai/static/js/sapling-sdk-v1.1.1.min.js"></script>
<script>
async function initializeSapling() {
  if (typeof Sapling === 'undefined') {
    throw new Error('Sapling SDK failed to load.');
  }

  const response = await fetch('/api/sapling-token', {
    credentials: 'same-origin',
  });

  if (!response.ok) {
    throw new Error(`Token request failed: ${response.status}`);
  }

  const {token} = await response.json();
  Sapling.init({key: token});
}

initializeSapling().catch(console.error);
</script>

The application-owned /api/sapling-token route should use one of the server-side examples in this directory and return {"token":"..."}.

Generated token text/plain

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.<base64url-claims>.<signature>

Return the compact token to the browser and pass it to Sapling.init as the key. Issue a fresh token after it expires; never send the private key.

How a JWT is structured

A JSON Web Token (JWT) is a compact, URL-safe way to pass signed claims between two parties, most often for authentication. It has three base64url-encoded parts separated by dots: header.payload.signature.

Header: The token type (JWT) and the signing algorithm, such as HS256 (HMAC with SHA-256) or RS256 (RSA).
Payload: The claims: statements about the subject plus metadata such as an expiry. Claims are registered (standard names below), public, or private names agreed between the two parties.
Signature: The encoded header and payload signed with a secret (or private key) using the header's algorithm. It proves who issued the token and that it hasn't been changed in transit.

Standard JWT claims

Sapling checks only sub and exp, but these are the registered claims you will see in HTML JWT libraries:

iss (issuer): who issued the token.
sub (subject): who the token is about. For Sapling, your public API key.
aud (audience): the recipients the token is intended for.
exp (expiration time): seconds since the Unix epoch after which the token must be rejected.
nbf (not before): seconds since the epoch before which the token must be rejected.
iat (issued at): when the token was issued, in seconds since the epoch.
jti (JWT ID): a unique identifier that lets a server reject replayed tokens.

Use a vetted JWT library

Sign tokens with an established, maintained cryptography library rather than hand-rolling HMAC and base64url encoding. Those libraries are peer-reviewed, handle edge cases such as algorithm confusion and clock skew, and get patched when new vulnerabilities appear.

Reference Frontend key management and JWT documentation All languages Choose another quickstart

About HTML

HTML, the HyperText Markup Language is used to design web pages to be rendered in browsers. Typically it is combined with CSS for styling and presentation and JavaScript for dynamic functionality.