Update Clerk JWT template

Update an existing JWT template in a connected Clerk application.

← All Clerk endpoints · Capability overview

PATCH/v1/clerk/jwt-templates/{template_id}

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

8 tokens

Update an existing 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.update_jwt_template

Parameters9 fields

clerk_instance_idstringOptional

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

template_idstringRequired

Clerk JWT template id (jtmp_...) to retrieve, update, or delete.

namestringOptional

Optional new unique template name.

claimsobjectOptional

Optional new JWT claims template as a JSON object.

lifetimeintegerOptional

Optional new token lifetime in seconds (30–315360000).

min 30, max 315360000

allowed_clock_skewintegerOptional

Optional new allowed clock skew in seconds (0–300).

min 0, max 300

custom_signing_keybooleanOptional

Optional flag to enable or disable a custom signing key.

signing_algorithmstringOptional

Optional custom signing algorithm.

signing_keystringOptional

Optional custom signing private key.

Response12 fields

jwt_templateobject

11 fields

Updated 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/{template_id}"
headers = {
    "Authorization": "Bearer YOUR_API_KEY",
}
payload = {
    "template_id": "jtmp_2abc123"
}

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

Example responses1 example

200A Clerk JWT template after an update.

updated_jwt_template.json

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