Create Clerk JWT template

Create a new JWT template in a connected Clerk application.

← All Clerk endpoints · Capability overview

POST/v1/clerk/jwt-templates

https://api.vee3.io/v1/clerk/jwt-templates

10 tokens

Create a new JWT template in a connected Clerk application.

Authorization

Send your API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

MCP

The same capability is available as an MCP tool on Vee3 hosted MCP.

Tool name

clerk.create_jwt_template

Parameters8 fields

clerk_instance_idstringOptional

Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.

namestringRequired

Unique JWT template name.

claimsobjectRequired

JWT claims template as a JSON object.

lifetimeintegerOptional

Token lifetime in seconds (30–315360000).

min 30, max 315360000

allowed_clock_skewintegerOptional

Allowed clock skew in seconds (0–300).

min 0, max 300

custom_signing_keybooleanOptional

Whether to use a custom signing key and algorithm.

signing_algorithmstringOptional

Custom signing algorithm (required when custom_signing_key is true).

signing_keystringOptional

Custom signing private key (required when custom_signing_key is true).

Response12 fields

jwt_templateobject

11 fields

Newly created Clerk JWT template summary.

idstring

Clerk JWT template id (jtmp_...).

namestring

Unique template name used when minting tokens from this template.

claimsobject

2 fields

JWT claims template as a JSON object (may include Clerk shortcodes).

audstring

Audience claim when set in the template.

rolestring

Role claim when set in the template.

lifetimeinteger

Token lifetime in seconds (exp claim offset from issuance time).

allowed_clock_skewinteger

Allowed clock skew in seconds for the nbf claim.

created_atinteger

Unix timestamp in milliseconds when the template was created.

updated_atinteger

Unix timestamp in milliseconds when the template was last updated.

signing_algorithmstring

Custom signing algorithm when custom_signing_key is enabled.

custom_signing_keyboolean

Whether this template uses a custom signing key and algorithm.

HTTP errors: clerk_connection_required, clerk_connection_not_found, clerk_connection_invalid, validation_error, unauthorized, payment_required

Example request

Python

import requests

url = "https://api.vee3.io/v1/clerk/jwt-templates"
headers = {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
}
payload = {
    "name": "billing-service",
    "claims": {"role":"org:member"}
}

response = requests.post(url, headers=headers, json=payload)
response.raise_for_status()
data = response.json()
print(data)

Example responses1 example

200A newly created Clerk JWT template.

created_jwt_template.json

{
  "jwt_template": {
    "id": "jtmp_2abc123",
    "name": "supabase",
    "claims": {
      "aud": "authenticated",
      "role": "authenticated"
    },
    "lifetime": 3600,
    "allowed_clock_skew": 5,
    "created_at": 1710000000000,
    "updated_at": 1710000000000,
    "signing_algorithm": null,
    "custom_signing_key": false
  }
}