Accounts are created by invitation. This page is for people who already have one. An account belongs to one person and one workspace.
Signing in
Sign in at zorl.cloud/login with your email address and password. The address is not case sensitive. After signing in you land on the hub, dashboard.zorl.cloud, or on the page you were sent from if a Zorl page sent you to sign in. A return address that is not one of Zorl Cloud's own is ignored and you land on the hub.
- A wrong password and an address with no account get the same answer, back on the sign-in page with "Invalid credentials. Try again."
- After 5 failed attempts from one address within 15 minutes, further attempts are answered
429with aRetry-Afterheader. A successful sign-in clears the count. - The form only works when it is posted from the sign-in page itself. A post from another site is answered
403. - A password is 12 to 256 characters.
Sessions
Signing in starts a session that lasts 30 days. The browser keeps it in one cookie, zorl_session, that JavaScript cannot read, that is sent only over https and that is set for all of zorl.cloud. That is why one sign-in covers the site, dashboard.zorl.cloud, mail.zorl.cloud and base.zorl.cloud. A page on one of those hosts that finds no valid session sends you to the sign-in page and brings you back afterwards.
Signing out clears the cookie and ends the session on the server, so a copy of the old cookie stops working too. A session also ends when the account's password is reset: every session is signed out at once.
Sessions are kept per sign-in, and a sign-in on the sign-in page and one made with the API are listed together. Each one has a user agent, an address and a last-seen time. You can list them and end the others with the API described under Signing in from code.
Resetting a password
Signed in, open Settings and choose Change password. Zorl mails a link to the address on the account. The button takes the address from your session, so it cannot send a link to anyone else, and it sends at most 3 links an hour for one account.
The sign-in page has no link for a forgotten password. If you cannot sign in, ask for the link with the API call under Signing in from code, or write to us from the contact page.
- The link works once and for one hour. Using one link also cancels any other reset link mailed before it.
- The new password is 12 to 256 characters.
- Setting it signs out every session on the account. The page then shows a one-time session token you can copy; to use the browser again, sign in with the new password.
- A link that was used, that is wrong or that is older than an hour gets a page that says so, and the link is not accepted again.
Verifying an address
An account has an email address and a verified time. Verifying proves the address is yours: Zorl mails a link, valid for 24 hours and for one use, and opening it marks the address verified. There is no button for this in the console yet, so it is requested with the API call under Signing in from code.
Nothing in Zorl Cloud asks for a verified address before you can sign in or use Mail and Base. The same call can start a change of address: give a new address, open the link mailed to it, and the account's address becomes that one.
Signing in from code
The same sessions can be made with the API on base.zorl.cloud. These calls need no API key: the session token that signing in returns is the credential. A session token starts with zss_ and is sent as Authorization: Bearer zss_your_session. It lasts 30 days and is not the same thing as an API key; keys for Mail and Base are made with it.
curl -X POST https://base.zorl.cloud/v1/auth/signin \
-H "Content-Type: application/json" \
-d '{"email": "[email protected]", "password": "your password"}'The answer is 200, and the token is shown once.
{
"user": {
"id": "0b7e0a1c-...",
"tenantId": "3f1c9a2e-...",
"email": "[email protected]",
"emailVerifiedAt": null,
"displayName": null,
"createdAt": "2026-11-12T09:30:00.000Z"
},
"tenant": {
"id": "3f1c9a2e-...",
"slug": "your-workspace",
"name": "Your workspace",
"plan": "free",
"createdAt": "2026-11-12T09:30:00.000Z"
},
"session": {
"token": "zss_...",
"sessionId": "9a6f6f1e-...",
"userId": "0b7e0a1c-...",
"tenantId": "3f1c9a2e-...",
"expiresAt": "2026-12-12T09:30:00.000Z"
}
}| Call | What it does | Answers |
|---|---|---|
POST /v1/auth/signin | Body {"email", "password"}. Starts a session. | 200, 400, 401, 429 |
GET /v1/auth/me | Returns the user and the workspace of the session. | 200, 401 |
GET /v1/auth/sessions | Lists your sessions. The one you are using has isCurrent true. | 200, 401 |
DELETE /v1/auth/sessions | Ends every other session and keeps this one. Answers {"revoked": 2}. | 200, 401 |
POST /v1/auth/signout | Ends this session. Answers the same whether or not the token was still valid. | 204, 400 |
POST /v1/auth/reset/request | Body {"email"}. Mails a reset link. | 202, 400, 429 |
POST /v1/auth/reset/confirm | Body {"token", "password"}. Sets the password. | 200, 400, 404, 410 |
POST /v1/auth/verify/request | Session required. Optional body {"email"}. | 202, 400, 401, 409, 429 |
POST /v1/auth/verify/confirm | Body {"token"}. | 200, 404, 410 |
{
"sessions": [
{
"id": "9a6f6f1e-...",
"userAgent": "curl/8.5.0",
"ip": "203.0.113.7",
"createdAt": "2026-11-12T09:30:00.000Z",
"lastSeenAt": "2026-11-12T09:30:00.000Z",
"expiresAt": "2026-12-12T09:30:00.000Z",
"isCurrent": true
}
]
}Resetting and verifying
curl -X POST https://base.zorl.cloud/v1/auth/reset/request \
-H "Content-Type: application/json" \
-d '{"email": "[email protected]"}'The answer is 202 with {"sent": true} whether or not the address has an account, so the call cannot be used to find out who has one. Then confirm with the token from the link.
curl -X POST https://base.zorl.cloud/v1/auth/reset/confirm \
-H "Content-Type: application/json" \
-d '{"token": "<token from the link>", "password": "a new password of 12 or more characters"}'The answer is 200 with the user, the workspace, a fresh session and sessionsRevoked, the number of sessions that were ended. A token that does not exist or was used is answered 404, an old one 410, and a password shorter than 12 characters 400.
verify/request answers 202 with sent, email, isEmailChange and expiresAt. If the mail could not be sent, sent is false and mailReason says why. A new address that belongs to another account is answered 409. verify/confirm answers 200 with the user, the workspace, a fresh session and emailChanged.
Sign-in, reset and verify requests share one limit: 5 attempts in 15 minutes from one address, then 429 with Retry-After. Verify requests are also limited to 5 in 15 minutes for one account.
What an invited account can do
An invited account is one person with one workspace. Settings shows the account's email address and says that nobody else can be added yet. From the hub at dashboard.zorl.cloud it can open:
- Zorl Mail: the inbox, sent mail, domains, addresses, API keys and webhooks. See the Mail page.
- Zorl Base: a console for its rows, and API keys. See the Base page.
- Settings: the email address, a button to change the password, and the theme.
- Billing: the account's plan and how much of the daily sending limit has been used.
Projects are not switched on yet, and the hub shows Zorl Hub, Zorl Deploy and @zorl/ai as coming, with no link. The consoles Zorl staff use are not open to an account: they answer it with 404 or 403.