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

[GH-ISSUE #6656] auth.api.signInEmail Works Without Headers But Docs Say Headers Required #27909

New Issue
Closed
opened 2026-04-17 19:11:44 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-17 19:11:44 -05:00
Owner
Copy Link

Originally created by @JeffreyLind3 on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6656

My codebase uses auth.api.signInEmail as follows and it works:

const response = await auth.api.signInEmail({
  body: {
    email: validatedEmail,
    password,
    callbackURL: "/sign-in", // Path user is directed to when clicking on verify email link in the email
  },
  asResponse: true,
});

However, the docs in https://www.better-auth.com/docs/authentication/email-password#sign-in say headers are required. I believe the docs are wrong.

Originally created by @JeffreyLind3 on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6656 My codebase uses `auth.api.signInEmail` as follows and it works: ```typescript const response = await auth.api.signInEmail({ body: { email: validatedEmail, password, callbackURL: "/sign-in", // Path user is directed to when clicking on verify email link in the email }, asResponse: true, }); ``` However, the docs in `https://www.better-auth.com/docs/authentication/email-password#sign-in` say `headers` are required. I believe the docs are wrong.
GiteaMirror added the locked label 2026-04-17 19:11:44 -05:00
GiteaMirror commented 2026-04-17 19:11:45 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Dec 10, 2025):

Hi there! Thanks for reporting this. Our email sign‐in API is designed to work in both scenarios—if no custom headers are provided, it still operates correctly because the default context is used. The documentation mentions headers for advanced use cases (for example, when you need to pass custom context like cookies or request metadata), but they aren’t strictly required in basic setups, which is why you’re seeing sign-in work without them [1].

As next steps, please confirm if you’re not using any custom header requirements in your environment. If you’d like to test a scenario with header overrides, try passing an empty or minimal header object and let us know if you notice any behavioral differences.

Tag @better-auth-agent if you would like an answer from the Agent—do you have any additional context or specific conditions where you expect headers to be needed?

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3635481211 --> @better-auth-agent[bot] commented on GitHub (Dec 10, 2025): Hi there! Thanks for reporting this. Our email sign‐in API is designed to work in both scenarios—if no custom headers are provided, it still operates correctly because the default context is used. The documentation mentions headers for advanced use cases (for example, when you need to pass custom context like cookies or request metadata), but they aren’t strictly required in basic setups, which is why you’re seeing sign-in work without them [[1]](https://github.com/better-auth/better-auth/issues/1183). As next steps, please confirm if you’re not using any custom header requirements in your environment. If you’d like to test a scenario with header overrides, try passing an empty or minimal header object and let us know if you notice any behavioral differences. Tag @better-auth-agent if you would like an answer from the Agent—do you have any additional context or specific conditions where you expect headers to be needed? _If you need more help, tag @better-auth-agent in a comment so I can respond._ <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) • [Discord](https://discord.gg/fG2XXEuQX3) • [GitHub](https://github.com/Skyvern-AI/Skyvern) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/fG2XXEuQX3) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/Skyvern-AI/Skyvern)
GiteaMirror commented 2026-04-17 19:11:45 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 10, 2025):

headers are required so we can get ipAddress, user agent...for the session

<!-- gh-comment-id:3637672490 --> @Bekacru commented on GitHub (Dec 10, 2025): headers are required so we can get ipAddress, user agent...for the session
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 locked
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#27909
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?