clerk-backend-api

Execute authenticated Clerk Backend REST API requests for user and organization administration.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Endsi3g/Uprising-AOS --skill clerk-backend-api-endsi3g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-backend-api
Source: https://github.com/Endsi3g/Uprising-AOS/tree/main/.agents/skills/clerk-backend-api
Command: npx skills add https://github.com/Endsi3g/Uprising-AOS --skill clerk-backend-api-endsi3g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you inspect Clerk Backend API endpoints and perform authenticated administration actions without guessing request formats or metadata field names, reducing trial-and-error and authorization failures.

Core Features & Use Cases

  • Discover endpoints by tag and inspect schemas: Browse API tags, enumerate endpoints for a tag, and view full endpoint definitions for planning correct calls.
  • Execute authenticated REST requests: Run safe GET requests and guide write operations with required parameter collection and response parsing.
  • Manage organizations, users, and metadata: Create organizations and invitations, list users, update user public/private/unsafe metadata with correct field naming and overwrite behavior, and handle destructive operations with explicit irreversibility warnings.

Quick Start

Ask: /clerk-backend-api execute get all users created in the last 7 days and show the parsed results with pagination guidance.

Frequently Asked Questions about clerk-backend-api

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

FAQPage Schema
How do I explore Clerk Backend API endpoints before making authenticated REST requests?

To explore the Clerk Backend API, you can browse API tags, enumerate endpoints for a specific tag, and view full endpoint schemas. This allows you to inspect request formats and metadata field names for planning correct REST calls.

How do I update user metadata using the Clerk Backend API safely?

You can update user public, private, or unsafe metadata through guided write operations that enforce mandatory scope checks. The process ensures correct field naming and handles overwrite behavior to prevent accidental data loss during metadata updates.

Can I list users created in the last 7 days with the Clerk Backend API?

Yes, you can execute authenticated GET requests to list users with specific time filters. The API parses the JSON response and provides pagination guidance to help you manage large sets of user records efficiently.

Do I need a secret key to create organizations and invitations in Clerk?

Yes, creating organizations and invitations requires CLERK_SECRET_KEY bearer authentication. The API enforces mandatory scope checks for these controlled write operations to ensure authorized administrative access.

What happens if I execute a destructive delete operation via the Clerk Backend API?

Executing a destructive delete operation via the Clerk Backend API is irreversible. The system explicitly warns about this irreversible behavior before completing the delete action to prevent accidental data removal.

Why does my Clerk Backend API request fail with an authorization error?

Clerk Backend API requests fail with authorization errors if the CLERK_SECRET_KEY bearer authentication is missing or invalid. Additionally, write and delete actions require mandatory scope checks to ensure the token has sufficient permissions.