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

Additional fields should also be there in response body #1437

New Issue
Closed
opened 2026-03-13 08:40:04 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-13 08:40:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @yscoder310 on GitHub (Jun 28, 2025).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Its really hard and a hassle to get the additional fields if have them in default schemas like for user schema

Describe the solution you'd like

can it be adde

Describe alternatives you've considered

it will help alot in later versions

Additional context

No response

Originally created by @yscoder310 on GitHub (Jun 28, 2025). ### Is this suited for github? - [ ] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Its really hard and a hassle to get the additional fields if have them in default schemas like for user schema ### Describe the solution you'd like can it be adde ### Describe alternatives you've considered it will help alot in later versions ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 08:40:04 -05:00
GiteaMirror commented 2026-03-13 08:40:06 -05:00
Author
Owner
Copy Link
Copy Source

@ping-maxwell commented on GitHub (Jul 1, 2025):

Hey what endpoints were you calling?

@ping-maxwell commented on GitHub (Jul 1, 2025): Hey what endpoints were you calling?
GiteaMirror commented 2026-03-13 08:40:06 -05:00
Author
Owner
Copy Link
Copy Source

@yscoder310 commented on GitHub (Jul 2, 2025):

I was calling sign-in/email endpoint Actually I wanted additional fields in sign in response body but I get it in only get session api response, for my use case I have to call first sign-in api and then get-session to get the addtional fields but I want it in first call like sign-in

@yscoder310 commented on GitHub (Jul 2, 2025): I was calling sign-in/email endpoint Actually I wanted additional fields in sign in response body but I get it in only get session api response, for my use case I have to call first sign-in api and then get-session to get the addtional fields but I want it in first call like sign-in
GiteaMirror commented 2026-03-13 08:40:06 -05:00
Author
Owner
Copy Link
Copy Source

@ping-maxwell commented on GitHub (Jul 4, 2025):

Yeah it's a limitation for now, same with the signUp endpoint.
In the future we hope to make that customizable.

@ping-maxwell commented on GitHub (Jul 4, 2025): Yeah it's a limitation for now, same with the signUp endpoint. In the future we hope to make that customizable.
GiteaMirror commented 2026-03-13 08:40:07 -05:00
Author
Owner
Copy Link
Copy Source

@erickweil commented on GitHub (Jul 4, 2025):

The way I see it, when analyzing the source code of signUp, signIn and username plugin to make my own plugin, I found the response is done explicitly choosing which fields to return to prevent "returned false" fields...

But this could be implemented by a helper function, such as getReturnedFields(user), or something similar, that both getSession and all routes who return user data would use.

As a workaround for now, it's possible to use a after hook reading the session to alter the response (using the setCookie response header)

@erickweil commented on GitHub (Jul 4, 2025): The way I see it, when analyzing the source code of signUp, signIn and username plugin to make my own plugin, I found the response is done explicitly choosing which fields to return to prevent "returned false" fields... But this could be implemented by a helper function, such as getReturnedFields(user), or something similar, that both getSession and all routes who return user data would use. As a workaround for now, it's possible to use a after hook reading the session to alter the response (using the setCookie response header)
GiteaMirror commented 2026-03-13 08:40:07 -05:00
Author
Owner
Copy Link
Copy Source

@ping-maxwell commented on GitHub (Jul 4, 2025):

Yeah, hooks are the way to go it seems.

@ping-maxwell commented on GitHub (Jul 4, 2025): Yeah, hooks are the way to go it seems.
GiteaMirror commented 2026-03-13 08:40:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 3, 2025):

Hi, @yscoder310. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested adding more fields to default response schemas (e.g., sign-in response) to reduce the need for multiple API calls.
  • Maintainer ping-maxwell acknowledged this limitation affects sign-in and sign-up endpoints and expressed hope for customizable responses in the future.
  • Contributor erickweil suggested a helper function to unify returned fields and recommended using after hooks as a workaround.
  • The discussion centers on improving usability by including additional user data in initial authentication responses.
  • The issue remains unresolved with no recent updates.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 3, 2025): Hi, @yscoder310. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested adding more fields to default response schemas (e.g., sign-in response) to reduce the need for multiple API calls. - Maintainer ping-maxwell acknowledged this limitation affects sign-in and sign-up endpoints and expressed hope for customizable responses in the future. - Contributor erickweil suggested a helper function to unify returned fields and recommended using after hooks as a workaround. - The discussion centers on improving usability by including additional user data in initial authentication responses. - The issue remains unresolved with no recent updates. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
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 labels enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#1437