Skip to main content
The Clerk replica implements 32 endpoints of the Backend API v1 for one application instance with email sign-in. Its key is clerk. It was tested with @clerk/backend.

Connect

Node
This is what ancha connect clerk --lang ts prints.

Endpoints

All 32 endpoints are partial. Anything else returns HTTP 501 with Clerk’s error shape and x-ancha-gap: 1.

Users

Organizations

Invitations and sessions

Starter data

The clerk-starter dataset is the instance Acme dashboard: the customers’ users and organizations. Twelve users in all, including Laura Kim from Acme with staff: true in her public metadata. Erin Walsh’s private metadata links her to HubSpot contact 30001. One instance-level invitation to security@bluefield-logistics.example is pending.

Checks

Clerk has no state checks. Use trace checks, for example { called: "POST /v1/organizations/*/invitations" } or { not_called: "DELETE /v1/users/*" }.

Limits

  • One application instance with email sign-in; phone numbers, web3 wallets, SAML and imported password hashes are coverage gaps.
  • Invitations are recorded, never emailed; pending ones expire on the scene clock.
  • Session tokens and JWT verification are not modeled; sessions can be listed and revoked.