github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Docs: Incorrect HTTP status code for unverified email error, 403 (docs) vs 401 (actual) #525

New Issue
Closed
opened 2026-03-13 07:50:58 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 07:50:58 -05:00
Owner
Copy Link

Originally created by @powdaze on GitHub (Jan 4, 2025).

In the docs for email and password, it is mentioned that:

If a user tries to sign in without verifying their email, you can handle the error and show a message to the user.

await authClient.signIn.emailAndPassword(
  {
    email: "email@example.com",
    password: "password",
  },
  {
    onError: (ctx) => {
      // Handle the error
      if (ctx.error.status === 403) {
        alert("Please verify your email address");
      }
      //you can also show the original error message
      alert(ctx.error.message);
    },
  }
);

However, when attempting to sign in with an unverified email, the error code is actually 401, not 403

{
    "message": "Email not verified",
    "code": "EMAIL_NOT_VERIFIED",
    "status": 401,
    "statusText": "UNAUTHORIZED"
}
Originally created by @powdaze on GitHub (Jan 4, 2025). In the [docs for email and password](https://www.better-auth.com/docs/authentication/email-password), it is mentioned that: >If a user tries to sign in without verifying their email, you can handle the error and show a message to the user. ```ts await authClient.signIn.emailAndPassword( { email: "email@example.com", password: "password", }, { onError: (ctx) => { // Handle the error if (ctx.error.status === 403) { alert("Please verify your email address"); } //you can also show the original error message alert(ctx.error.message); }, } ); ``` However, when attempting to sign in with an unverified email, the error code is actually 401, not 403 ```ts { "message": "Email not verified", "code": "EMAIL_NOT_VERIFIED", "status": 401, "statusText": "UNAUTHORIZED" } ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#525
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?