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

[GH-ISSUE #2486] How to pass additionaFields / custom data via signUp.email()? #9219

New Issue
Closed
opened 2026-04-13 04:37:45 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:37:45 -05:00
Owner
Copy Link

Originally created by @allantatter on GitHub (Apr 30, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2486

Is this suited for github?

  • Yes, this is suited for github

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

No response

Describe the solution you'd like

I'd like to include additional fields (e.g. marketingCommunicationAccepted boolean) in my signup form that are included as additionalFields on user object. I was hoping to be able to pass marketingCommunicationAccepted in signup method and handle it via databaseHooks.user.create.before/after.

Is such a thing already possible?

Describe alternatives you've considered

Multiple API requests from the frontend is not a good solution therefore I'd need to move signup() method calling to the backend but it's complicated as signup method create cookies and I'd have to proxy Set-Cookie headers manually.

Additional context

No response

Originally created by @allantatter on GitHub (Apr 30, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2486 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like I'd like to include additional fields (e.g. marketingCommunicationAccepted boolean) in my signup form that are included as additionalFields on user object. I was hoping to be able to pass marketingCommunicationAccepted in signup method and handle it via `databaseHooks.user.create.before/after`. Is such a thing already possible? ### Describe alternatives you've considered Multiple API requests from the frontend is not a good solution therefore I'd need to move signup() method calling to the backend but it's complicated as signup method create cookies and I'd have to proxy Set-Cookie headers manually. ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:37:45 -05:00
GiteaMirror commented 2026-04-13 04:37:48 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jul 30, 2025):

Hi, @allantatter. 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 the ability to pass custom fields (e.g., marketingCommunicationAccepted boolean) directly through the signUp.email() method.
  • The goal is to have these fields included in the user object for database hook processing.
  • You want to avoid multiple frontend API calls or moving signup logic to the backend.
  • Currently, this functionality is not confirmed as supported.
  • There have been no comments or updates on this issue so far.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of better-auth by commenting on this issue.
  • If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3136951941 --> @dosubot[bot] commented on GitHub (Jul 30, 2025): Hi, @allantatter. 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 the ability to pass custom fields (e.g., marketingCommunicationAccepted boolean) directly through the signUp.email() method. - The goal is to have these fields included in the user object for database hook processing. - You want to avoid multiple frontend API calls or moving signup logic to the backend. - Currently, this functionality is not confirmed as supported. - There have been no comments or updates on this issue so far. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of better-auth by commenting on this issue. - If I do not hear back within 7 days, I will automatically close this issue. 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 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#9219
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?