API Quickstart

Everything below is a raw curl call against our API — no SDK, no dashboard clicking. This is exactly what your own backend or CLI would run to provision a tenant, add a user, and get back a JWT.

Before you start: get an API key

Create your free account — check your email and set a password to activate it.
Log in to the dashboard, then go to Account Settings → API Keys → New Key.
Copy the key (it's only shown once) and export it in your terminal:

export API_KEY=umc_your_key_here

Every curl call below sends this key as Authorization: Bearer $API_KEY — run the export once per terminal session and every block is copy-pasteable as-is.

slug becomes part of every login call — pick something short and stable, like my-app-prod.

curl -X POST https://api.authjet.dev/api/v1/account/tenants \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My App",
    "slug": "my-app"
  }'

The response includes the new tenant's id. Export it — the next calls need it:

export TENANT_ID=the-id-from-the-response
export TENANT_SLUG=my-app

I've created a tenant and exported TENANT_ID

Pick one:

Set a password right awayYou collect the password yourself (your own signup form). User is active immediately, no email round-trip.Send an invite insteadWe email a token to a page on your app; your page collects the password and calls us back.

One call — the user is active as soon as this returns.

curl -X POST https://api.authjet.dev/api/v1/account/tenants/$TENANT_ID/users \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com",
    "password": "SuperSecret123",
    "full_name": "Ada Lovelace"
  }'

Point callback_url at our hosted accept-invite page and there's nothing else to build — the user clicks the link, sets a password there, and is active immediately.

curl -X POST https://api.authjet.dev/api/v1/account/tenants/$TENANT_ID/users/invite \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com",
    "full_name": "Ada Lovelace",
    "callback_url": "https://api.authjet.dev/login/'"$TENANT_SLUG"'/accept-invite?token={token}"
  }'

Building your own accept-invite page instead? Point callback_url at it — read the token query param when the user lands there, collect a password, and call this from your backend to activate them:

curl -X POST https://api.authjet.dev/api/v1/auth/invite/accept \
  -H "Content-Type: application/json" \
  -d '{
    "token": "the-token-from-the-query-string",
    "new_password": "SuperSecret123"
  }'

My user exists and can sign in with a password

curl -X POST https://api.authjet.dev/api/v1/auth/login/jwt \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com",
    "password": "SuperSecret123",
    "tenant_slug": "'"$TENANT_SLUG"'"
  }'

You get back a tenant-scoped access_token — a JWT carrying the user's id, tenant, and role. Verify it with your API key's secret and you're authenticated, no session lookup required.

I got back a JWT

Every tenant gets a hosted, brandable login page — no frontend code required. Open this URL (swap in your TENANT_SLUG) and log in with the same email and password from step 2:

https://api.authjet.dev/login/$TENANT_SLUG

No redirect_uri means you'll land on a page showing the exact JWT your app would have received — same token, same claims, this time through our UI instead of curl. Add a redirect_uri whenever you're ready to send it to your own app instead.

I saw my JWT on the hosted page

Next: protect your backend

Your API receives these tokens from your app. Verify them in a few lines of Node.js, Python, Java, .NET, Go, PHP or Ruby.

How to verify access tokens →All docs

Ready to do this for real?

Create your free account