clerk-backend-api

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

Updated Sep 11, 2026

Search Tags:#authentication #openapi #rest api #user management #curl #organizations #clerk

Ready to run

npx skills add https://github.com/celeroncoder/skills --skill clerk-backend-api-celeroncoder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/celeroncoder/skills/tree/main/clerk-backend-api
Command: npx skills add https://github.com/celeroncoder/skills --skill clerk-backend-api-celeroncoder

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, which normally means digging through OpenAPI specs and documentation before every call. ## Core Features & Use Cases - Endpoint Discovery: Browse API tags and inspect full endpoint schemas extracted from the official Clerk OpenAPI specs, including referenced components. - Fast-Path Operations: Execute common tasks immediately with ready-made templates for listing users, creating organizations, inviting members, updating metadata, and deleting users. - Safety Guardrails: Mandatory scope checks before write operations and explicit irreversibility warnings before DELETE requests. - Use Case: Ask to create an organization called 'Acme Corp' and invite [email protected] as an admin, and the Skill runs the two-step POST /v1/organizations and invitation flow with your CLERK_SECRET_KEY. ## Quick Start Ask the agent 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 Clerk users from the 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 with a gt: timestamp filter to narrow results 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 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, private_metadata is server-only for both read and write, and unsafe_metadata is readable and writable by both client and server. Use public for plan tiers, private for Stripe IDs, and avoid sensitive data in unsafe.

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 requests 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, DELETE /v1/users/{user_id} is irreversible and permanently destroys the user record, all sessions, all memberships, and all associated data. The Skill requires explicit confirmation and a scope check before executing any delete.