clerk-backend-api

Browse and execute Clerk Backend REST API endpoints with authenticated curl requests.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-backend-api-rajaryan1726
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/Rajaryan1726/ai-code-review-system/tree/main/client/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-backend-api-rajaryan1726

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Working with the Clerk Backend REST API requires knowing exact endpoint paths, request schemas, and authentication details. This Skill removes the need to dig through OpenAPI specs manually by letting you browse tags, inspect endpoint definitions, and execute authenticated requests directly, with built-in safety checks for write and delete operations. ## Core Features & Use Cases - Endpoint Discovery: Fetch the latest Clerk OpenAPI spec, list all tags, and inspect full endpoint schemas including referenced components. - 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, explicit irreversibility warnings before DELETE requests, and guidance on public vs private vs unsafe metadata. - Use Case: You need to create an organization called 'Acme Corp' and invite an admin. The Skill runs the two-step API flow (POST /v1/organizations then POST /v1/organizations/{id}/invitations) with your CLERK_SECRET_KEY and parses the JSON responses for you. ## 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 Clerk users from the Backend API?▼

Send a GET request to https://api.clerk.com/v1/users with your CLERK_SECRET_KEY as a Bearer token. Use limit and offset for pagination, order_by for sorting, and created_at with gt: or lt: Unix-millisecond timestamps to filter by signup date.

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

First POST to /v1/organizations with a name and created_by user ID, then extract the returned organization ID and POST to /v1/organizations/{id}/invitations with the invitee's 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 and roles. private_metadata is server-only for secrets like Stripe IDs. unsafe_metadata is client-writable, so avoid storing sensitive data there.

Why does updating Clerk user metadata delete my existing fields?▼

Clerk metadata updates overwrite the entire object rather than merging. Read the existing user first with getUser, spread the current metadata into your new object, 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 counting against the limit, so use auth() when you only need session claims.

Can I delete a Clerk user through the Backend API?▼

Yes, via DELETE /v1/users/{user_id} with Bearer authentication, but the action is irreversible and destroys the user record, all sessions, memberships, and associated data. The Skill requires explicit confirmation and a CLERK_BAPI_SCOPES check including write and delete before executing.