clerk-backend-api

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/DimonikRV/ghost-pilot-project --skill clerk-backend-api-dimonikrv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/DimonikRV/ghost-pilot-project/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/DimonikRV/ghost-pilot-project --skill clerk-backend-api-dimonikrv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Working with the Clerk Backend API requires knowing endpoint paths, request schemas, and authentication details, and mistakes on write or delete operations can permanently destroy user data. This Skill provides ready-to-use request templates, spec-driven endpoint discovery, and mandatory safety checks before any destructive call. ## Core Features & Use Cases - Fast-path templates: Pre-built curl and SDK snippets for common operations like listing users, creating organizations, inviting members, updating metadata, and deleting users. - Spec-driven exploration: Browse API tags, list endpoints per tag, and inspect full endpoint schemas extracted from the official Clerk OpenAPI specs. - Safety guardrails: Mandatory CLERK_SECRET_KEY and CLERK_BAPI_SCOPES checks before writes, plus irreversibility warnings before DELETE requests. - Use Case: You need to invite a new admin to an organization. The Skill creates the organization via POST /v1/organizations, extracts the org ID, and sends the invitation with the org:admin role in two authenticated calls. ## Quick Start Ask the assistant to list all Clerk users who signed up in the last 7 days using the 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 /v1/users with your CLERK_SECRET_KEY as a Bearer token in the Authorization header. Use limit and offset for pagination, order_by for sorting, and created_at filters to narrow results by signup date.

How do I create an organization and invite a member with 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 and roles. Private metadata is server-only for sensitive identifiers. Unsafe metadata is client-writable and should never hold sensitive data.

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

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

What are the Clerk Backend API rate limits?▼

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

Is deleting a Clerk user via the API reversible?▼

No, deleting a user with DELETE /v1/users/{user_id} is irreversible. It permanently destroys the user record, all sessions, all memberships, and all associated data, so explicit confirmation is required before executing.