Clerk

Clerk Signups API

Sign-up objects track the progress of a sign-up attempt and store any field collected from user input.

GitHub OpenAPI
Business capability
Identity & Access Management BC-620.20

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /sign_ups/{id} Retrieve a sign-up from the backend · Retrieve a Sign-up by ID #
Ask an LLM
“Can my server look up a sign-up attempt by its ID?”
“What fields has a user filled in on a sign-up so far, seen from the backend?”
Tell an agent
Retrieve sign-up {id} using the backend API.
Show the server-side details of sign-up {id}.
PATCH /sign_ups/{id} Set a sign-up's external ID or custom action · Update a Sign-up #
Ask an LLM
“How do I attach my own external ID to a sign-up from my backend?”
“Can the backend mark a sign-up's custom action as done?”
Tell an agent
Set external ID {external_id} on sign-up {id}.
Mark the custom action complete on sign-up {id} from the backend.
POST /v1/client/sign_ups Start a sign-up on the current client · Create Sign-up #
Ask an LLM
“How do I register a new user with email and password?”
“Can a sign-up be started from an invitation ticket or a web3 wallet?”
Tell an agent
Sign up {email_address} with password {password}.
Create a sign-up for {first_name} {last_name} with username {username}.
GET /v1/client/sign_ups/{sign_up_id} Get the current client's sign-up · Get Sign-up #
Ask an LLM
“Which fields are still missing on my in-progress sign-up?”
“Can the browser fetch its own sign-up by ID?”
Tell an agent
Get my sign-up {sign_up_id}.
Show missing requirements on sign-up {sign_up_id}.
PATCH /v1/client/sign_ups/{sign_up_id} Add details to an in-progress sign-up · Update Sign-up #
Ask an LLM
“How do I add a phone number or username to a sign-up already started?”
“Can I fill in missing fields on a sign-up before verifying it?”
Tell an agent
Add phone number {phone_number} to sign-up {sign_up_id}.
Set username {username} on in-progress sign-up {sign_up_id}.
POST /v1/client/sign_ups/{sign_up_id}/prepare_verification Send a verification code for a sign-up · Prepare Sign-up Identification Verification #
Ask an LLM
“How do I send the new user a code to verify their email during sign-up?”
“Can sign-up verification use a phone code or an email link?”
Tell an agent
Send a {strategy} verification for sign-up {sign_up_id}.
Email a verification code for sign-up {sign_up_id}.
POST /v1/client/sign_ups/{sign_up_id}/attempt_verification Submit a sign-up verification code · Attempt Sign-up Identification Verification #
Ask an LLM
“How do I complete sign-up with the code the user received?”
“What does a sign-up need to verify a web3 wallet signature?”
Tell an agent
Verify sign-up {sign_up_id} with code {code}.
Attempt {strategy} verification on sign-up {sign_up_id} using {code}.

Documentation

📖
Documentation
https://clerk.com/docs/reference/backend-api
📖
APIReference
https://clerk.com/docs/reference/backend-api
📖
GettingStarted
https://clerk.com/docs/quickstarts/overview
📖
Authentication
https://clerk.com/docs/backend-requests/making/jwt-templates
📖
Documentation
https://clerk.com/docs
📖
Documentation
https://clerk.com/docs/webhooks/overview

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/clerk-com/refs/heads/main/openapi/clerk-com-signups-api-openapi.yml

Other Resources

🔗
SpectralRuleset
https://raw.githubusercontent.com/api-evangelist/clerk-com/refs/heads/main/rules/clerk-rules.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/clerk-com:clerk-com-signups-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

clerk-com-signups-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Clerk Com Sign Ups API
  termsOfService: https://clerk.com/terms
  x-logo:
    url: https://clerk.com/_next/image?url=%2Fimages%2Fclerk-logo.svg&w=96&q=75
    altText: Clerk docs
    href: https://clerk.com/docs
  version: '1.0'
  description: 'Operations tagged Sign Ups across 2 of this provider''s published API definitions: clerk-backend-api-openapi.yml, clerk-frontend-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.clerk.com/v1
- url: https://{domain}.clerk.accounts.dev
  variables:
    domain:
      default: example-destined-camel-13
      description: Your Development Instance Frontend API Domain.
tags:


# --- truncated at 32 KB (73 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/clerk-com/refs/heads/main/openapi/clerk-com-signups-api-openapi.yml