clerk-backend-api

Browse, inspect, and execute Clerk Backend REST API endpoints with curl.

2|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/zester4/zilmate --skill clerk-backend-api-zester4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/zester4/zilmate/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/zester4/zilmate --skill clerk-backend-api-zester4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Working with the Clerk Backend API requires knowing the correct endpoints, request schemas, and authentication patterns. This Skill removes the guesswork by letting you browse the official OpenAPI spec, inspect endpoint details, and execute authenticated requests directly, with built-in safety checks for write and delete operations. ## Core Features & Use Cases - Endpoint Discovery: Browse API tags and fetch full endpoint definitions (parameters, request bodies, referenced schemas) from the official Clerk OpenAPI specs. - Fast-Path Operations: Pre-built templates for common tasks like listing users, creating organizations, inviting members, updating user metadata, and deleting users. - Safety Guardrails: Mandatory scope checks (CLERK_BAPI_SCOPES) before write operations and explicit irreversibility warnings before DELETE requests. - Use Case: You need to create an organization called 'Acme Corp' and invite an admin. The Skill runs the two-step flow: POST /v1/organizations, extracts the org ID, then POSTs the invitation with the org:admin role. ## Quick Start Ask the assistant to list all users who signed up in the last 7 days using the Clerk Backend API.

Frequently Asked Questions about clerk-backend-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list users from the Clerk Backend API?

Send a GET request to https://api.clerk.com/v1/users with your CLERK_SECRET_KEY as a Bearer token in the Authorization header. Use limit and offset query parameters for pagination, and order_by or created_at filters to narrow results.

How do I create an organization and invite a member via the Clerk API?

First POST to /v1/organizations with a name and created_by user ID, then extract the organization ID from the response. Next, POST to /v1/organizations/{id}/invitations with the email_address and a role of org:admin or org:member.

What is the difference between public, private, and unsafe metadata in Clerk?

public_metadata is readable by client and server but writable only server-side, ideal for plan tiers. private_metadata is server-only for sensitive data like Stripe IDs. unsafe_metadata is client-writable and should never hold sensitive information.

Why does updating Clerk user metadata delete my existing fields?

Clerk metadata updates replace the entire object rather than merging. Read the existing metadata with getUser first, spread it into a new object with your additions, then call updateUser with the merged result.

What are the Clerk Backend API rate limits?

Production allows 1,000 requests per 10 seconds while development allows 100 per 10 seconds. Note that currentUser() makes a real API call that counts against the limit, so use auth() when you only need session claims.

Can I delete a Clerk user through the Backend API?

Yes, send a DELETE request to /v1/users/{user_id} with your secret key. This action is irreversible and permanently destroys the user record, all sessions, memberships, and associated data, so explicit confirmation is required first.