clerk-backend-api

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

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/paramcodes/autobro --skill clerk-backend-api-paramcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/paramcodes/autobro/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/paramcodes/autobro --skill clerk-backend-api-paramcodes

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. This Skill lets you discover endpoints from the official OpenAPI specs and execute authenticated requests for user, organization, and metadata management without memorizing the API surface. ## Core Features & Use Cases - Endpoint Discovery: Browse tags and inspect full endpoint schemas extracted from Clerk's versioned OpenAPI specifications. - Fast-Path Operations: Run common tasks immediately, such as listing users, creating organizations, inviting members, and updating user metadata. - Safe Write Operations: Enforces mandatory checks on CLERK_SECRET_KEY and CLERK_BAPI_SCOPES before any POST, PATCH, PUT, or DELETE, with explicit irreversibility warnings for deletions. - Use Case: Ask to create an organization called 'Acme Corp' and invite an admin, and the Skill runs the two-step API flow, extracting the organization ID and sending the invitation with the correct role. ## 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 like gt:TIMESTAMP to narrow results by signup date.

How to update user metadata with the Clerk API?▼

Send a PATCH request to /v1/users/{user_id} with a JSON body containing public_metadata, private_metadata, or unsafe_metadata. Public metadata is readable by the client, private is server-only, and unsafe is client-writable, so choose based on sensitivity.

Why does updating Clerk user metadata delete 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 to preserve existing fields.

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.

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

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

What credentials does the Clerk Backend API require?▼

Every request requires CLERK_SECRET_KEY (starting with sk_) sent as a Bearer token. Write operations additionally check CLERK_BAPI_SCOPES for write or delete permissions, which can be bypassed with an admin flag.