This feature is available only on the Enterprise Plan of Portkey.

Portkey supports JWT-based authentication in addition to API Key authentication. Clients can authenticate API requests using a JWT token, which is validated against a configured JWKS (JSON Web Key Set). This guide explains the requirements and setup process for JWT authentication in Portkey.

Validate JWT Token (Guardarail)

Validate your JWT Token before making a LLM request using Portkey.

​
Configuring JWT Authentication

JWT authentication can be configured under Admin Settings → Organisation → Authentication.

​
JWKS Configuration

To validate JWTs, you must configure one of the following:

  • JWKS URL: A URL from which the public keys will be dynamically fetched.
  • JWKS JSON: A static JSON containing public keys.

​
JWT Requirements

​
Supported Algorithm

  • JWTs must be signed using RS256 (RSA Signature with SHA-256).

​
Required Claims

Your JWT payload must contain the following claims:

Claim KeyDescription
portkey_oid / organisation_idUnique identifier for the organization.
portkey_workspace / workspace_slugIdentifier for the workspace.
scope / scopesPermissions granted by the token.

​
User Identification

Portkey identifies users in the following order of precedence for logging and metrics:

  1. email_id
  2. sub
  3. uid

​
Authentication Process

  1. The client sends an HTTP request with the JWT in the x-portkey-api-key header:

    x-portkey-api-key: <JWT_TOKEN>

  2. The server validates the JWT:

    • Verifies the signature using the JWKS.
    • Checks if the token is expired.
    • Ensures the required claims are present.

  3. If valid, the request is authenticated, and user details are extracted for authorization and logging.

  4. If invalid, the request is rejected with an HTTP 401 Unauthorized response.

​
Authorization & Scopes

Once the JWT is validated, the server checks for the required scope. Scopes can be provided in the JWT as either a single string or an array of strings using the scope or scopes claim.

Scopes can also be prefixed with portkey. (e.g., portkey.completions.write).

JWT tokens with appropriate scopes function identically to workspace API keys, providing access to workspace-specific operations. They cannot be used as organization API keys, which have broader administrative permissions across all workspaces.

​
Example JWT Payload

{
  "portkey_oid" : "org_123456",
  "portkey_workspace": "workspace_abc",
  "scope": ["completions.write", "logs.view"],
  "email_id": "user@example.com",
  "sub": "user-123",
  "exp": 1735689600
}

​
Making API Calls with JWT Authentication

Once you have a valid JWT token, you can use it to authenticate your API calls to Portkey. Below are examples showing how to use JWT authentication with different SDKs.

Install the Portkey SDK with npm

npm install portkey-ai

import Portkey from 'portkey-ai';

const client = new Portkey({
  apiKey: '<JWT_TOKEN>', // Use JWT token instead of API key
});

async function main() {
  const response = await client.chat.completions.create({
    messages: [{ role: "user", content: "Hello, how are you today?" }],
    model: "gpt-4o",
  });

  console.log(response.choices[0].message.content);
}

main();

​
Caching & Token Revocation

  • JWTs are cached until they expire to reduce validation overhead.