Clerk Sign Ups API
Sign-up objects track the progress of a sign-up attempt and store any field collected from user input.
Clerk Sign Ups API is one of 104 APIs that Clerk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Signups. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.
This API exposes 7 operations across 5 paths, and defines 44 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against 2 base URLs: https://api.clerk.com/v1, https://{domain}.clerk.accounts.dev.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
Clerk Sign Ups API declares
6 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (sk_bearerAuth).
An API key is passed in the cookie as __client (ProductionBrowser).
An API key is passed in the query as __dev_session (DevBrowser).
It accepts HTTP bearer tokens (ProductionNativeApp).
An API key is passed in the query as _is_native (ProductionNativeFlag).
It accepts HTTP basic authentication (ClientCredentials).
bearerAuth— Secret key, obtained under "API Keys" in the Clerk Dashboard.ProductionBrowser— The Client API token sent in the form of a browser cookie. Used to authenticate production browser applications.DevBrowser— A Dev Browser API token sent as a query parameter. Used to authenticate only dev instances. To generate a dev instance API token you must first make a request…ProductionNativeApp— The Client API token sent in the Authorization header. Used to authenticate native applications.ProductionNativeFlag— If sent and the value is true, it instructs the server to parse the API token from the Authorization header. It should always be set to true when using the Aut…ClientCredentials— HTTP Basic Authentication using Client ID as username and Client Secret as password.
Paths & Operations 7
Across 5 paths, the API surfaces 7 operations — 2 GET, 2 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Sign-up objects track the progress of a sign-up attempt and store any field collected from user input.
Schemas 44
The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are Client.User (42 properties), SignUp (25 properties), Client.SignUp (23 properties), ExternalAccountWithVerification (19 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Clerk 12
Other APIs Clerk publishes across the network.
This is an independent, third-party profile of Clerk Sign Ups API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.