[GH-ISSUE #3602] Optional data field in auth.api.createUser() is non-functional #9659

New Issue

GiteaMirror · 2026-04-13T05:16:15-05:00

GiteaMirror commented

2026-04-13 05:16:15 -05:00

Originally created by @eaoliver on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3602

Is this suited for github?

Yes, this is suited for github

To Reproduce

The optional data field in the auth.api.createUser function enabled by the admin plugin does not appear to function.

Following the example on: https://www.better-auth.com/docs/plugins/admin#create-user

const newUser = await auth.api.createUser({
    body: {
        email: "user@example.com", // required
        password: "some-secure-password", // required
        name: "James Smith", // required
        role: "user",
        data: { customField: "customValue" },
    },
});

No custom data is stored.

I tried adding a data column to the users table and a column corresponding to the customField.

Current vs. Expected behavior

Any custom data when creating a new is not stored.

What version of Better Auth are you using?

1.3.3

Provide environment information

Node 20

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
  database: drizzleAdapter(db, {
    //debugLogs: true,
    provider: "pg",
    schema: {
      users: users,
      accounts: accounts,
      sessions: sessions,
      verifications: verifications,
      two_factors: twoFactors,
      apikeys: apikeys,
    },
    usePlural: true,
  }),
  plugins: [
    apiKey(),
    twoFactor(),
    admin(),
  ]
});

Additional context

No response

Originally created by @eaoliver on GitHub (Jul 25, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3602 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce The optional data field in the `auth.api.createUser` function enabled by the `admin` plugin does not appear to function. Following the example on: https://www.better-auth.com/docs/plugins/admin#create-user ``` const newUser = await auth.api.createUser({ body: { email: "user@example.com", // required password: "some-secure-password", // required name: "James Smith", // required role: "user", data: { customField: "customValue" }, }, }); ``` No custom data is stored. I tried adding a `data` column to the `users` table and a column corresponding to the customField. ### Current vs. Expected behavior Any custom data when creating a new is not stored. ### What version of Better Auth are you using? 1.3.3 ### Provide environment information ```bash Node 20 ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, database: drizzleAdapter(db, { //debugLogs: true, provider: "pg", schema: { users: users, accounts: accounts, sessions: sessions, verifications: verifications, two_factors: twoFactors, apikeys: apikeys, }, usePlural: true, }), plugins: [ apiKey(), twoFactor(), admin(), ] }); ``` ### Additional context _No response_

GiteaMirror added the locked bug labels 2026-04-13 05:16:15 -05:00

GiteaMirror closed this issue

2026-04-13 05:16:16 -05:00

GiteaMirror commented

2026-04-13 05:16:16 -05:00

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

The reason custom data from the data field in createUser isn't being stored is that Better Auth only persists fields that are explicitly defined in your user schema. Just adding a column to your database isn't enough—custom fields must be registered in your auth config using the additionalFields property. This applies whether you want a single JSON data column or individual custom fields.

To store custom data, update your auth config like this:

export const auth = betterAuth({
  // ...other config
  user: {
    additionalFields: {
      // For a JSON 'data' column:
      data: { type: "json", required: false },
      // Or for individual fields:
      customField: { type: "string", required: false }
    }
  }
});

After updating your config, run the Better Auth CLI to update your database schema:

npx @better-auth/cli generate
# or, if using the built-in Kysely adapter:
npx @better-auth/cli migrate

Now, when you call createUser with a data property (or any custom field you've defined), it will be persisted as expected. You can find more details and examples in the official documentation.

If you want to store arbitrary JSON data, define a data field of type "json" in additionalFields. If you want to store individual custom fields, define each one separately. The admin plugin's data property is just a convenience for passing these extra fields, but they must be present in your schema to be saved source.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 25, 2025):  The reason custom data from the `data` field in `createUser` isn't being stored is that Better Auth only persists fields that are explicitly defined in your user schema. Just adding a column to your database isn't enough—custom fields must be registered in your auth config using the `additionalFields` property. This applies whether you want a single JSON `data` column or individual custom fields. To store custom data, update your auth config like this: ```typescript export const auth = betterAuth({ // ...other config user: { additionalFields: { // For a JSON 'data' column: data: { type: "json", required: false }, // Or for individual fields: customField: { type: "string", required: false } } } }); ``` After updating your config, run the Better Auth CLI to update your database schema: ``` npx @better-auth/cli generate # or, if using the built-in Kysely adapter: npx @better-auth/cli migrate ``` Now, when you call `createUser` with a `data` property (or any custom field you've defined), it will be persisted as expected. You can find more details and examples in the [official documentation](https://better-auth.com/docs/concepts/database). If you want to store arbitrary JSON data, define a `data` field of type `"json"` in `additionalFields`. If you want to store individual custom fields, define each one separately. The admin plugin's `data` property is just a convenience for passing these extra fields, but they must be present in your schema to be saved [source](https://better-auth.com/docs/concepts/database).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/36cadb8a-58a3-4794-8e3b-532919707b4d?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3602)

GiteaMirror commented

2026-04-13 05:16:17 -05:00

@eaoliver commented on GitHub (Jul 25, 2025):

Amazing. Thank you @dosu.

@eaoliver commented on GitHub (Jul 25, 2025): Amazing. Thank you @dosu.

GiteaMirror commented

2026-04-13 05:16:18 -05:00

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

You're welcome!

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 25, 2025):  You're welcome!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1612ef22-d48b-4deb-8611-563d5aff08f6?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3602)

GiteaMirror commented

2026-04-13 05:16:18 -05:00

@eaoliver commented on GitHub (Jul 25, 2025):

For what it's worth @dosu, using "json" as a type produces this error when attempting to generate the new schema:

% npx @better-auth/cli generate
⠋ preparing schema...file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:480
      return typeMap[type][databaseType];
                          ^

TypeError: Cannot read properties of undefined (reading 'pg')
    at getType (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:480:27)
    at file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:508:18
    at Array.map (<anonymous>)
    at generateDrizzleSchema (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:506:28)
    at generateSchema (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:741:12)
    at Command.generateAction (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:784:24)

It's also causing the following error when calling auth.api.verifyApiKey:

Type error: Property 'verifyApiKey' does not exist on type 'InferAPI<{ ok: { <AsResponse extends boolean = false, ReturnHeaders extends boolean = false>(inputCtx_0?: ({ body?: undefined; } & { method?: "GET" | undefined; } & { query?: Record<string, any> | undefined; } & { params?: Record<string, any> | undefined; } & { ...; } & { ...; } & { ...; } & { ...; }) | undefined): ...'.

> 80 |       const verifyData = await auth.api.verifyApiKey({

@eaoliver commented on GitHub (Jul 25, 2025): For what it's worth @dosu, using "json" as a type produces this error when attempting to generate the new schema: ``` % npx @better-auth/cli generate ⠋ preparing schema...file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:480 return typeMap[type][databaseType]; ^ TypeError: Cannot read properties of undefined (reading 'pg') at getType (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:480:27) at file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:508:18 at Array.map (<anonymous>) at generateDrizzleSchema (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:506:28) at generateSchema (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:741:12) at Command.generateAction (file:///Users/eaoliver/.npm/_npx/167ca1f116d365e6/node_modules/@better-auth/cli/dist/index.mjs:784:24) ``` It's also causing the following error when calling `auth.api.verifyApiKey`: ``` Type error: Property 'verifyApiKey' does not exist on type 'InferAPI<{ ok: { <AsResponse extends boolean = false, ReturnHeaders extends boolean = false>(inputCtx_0?: ({ body?: undefined; } & { method?: "GET" | undefined; } & { query?: Record<string, any> | undefined; } & { params?: Record<string, any> | undefined; } & { ...; } & { ...; } & { ...; } & { ...; }) | undefined): ...'. > 80 | const verifyData = await auth.api.verifyApiKey({ ```

GiteaMirror commented

2026-04-13 05:16:19 -05:00

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

The Drizzle adapter in Better Auth doesn't support "json" as a type for additionalFields, which is why you see that TypeError—only "string", "number", "boolean", "date", "number[]", and "string[]" are supported. To store custom user data, you can either define each custom field explicitly as its own string/number/etc. field in additionalFields, or (if you need to store arbitrary JSON) serialize your object to a string and store it in a "string" field, then parse it in your app logic. See the database extension docs for examples.

For the verifyApiKey TypeScript error: the correct usage is auth.apiKey.verifyApiKey, not auth.api.verifyApiKey. The plugin APIs are namespaced, so make sure you're calling the method from the right place. If you still see type errors, double-check that the apiKey plugin is enabled in your config and that your types are up to date.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 25, 2025):  The Drizzle adapter in Better Auth doesn't support `"json"` as a type for `additionalFields`, which is why you see that TypeError—only `"string"`, `"number"`, `"boolean"`, `"date"`, `"number[]"`, and `"string[]"` are supported. To store custom user data, you can either define each custom field explicitly as its own string/number/etc. field in `additionalFields`, or (if you need to store arbitrary JSON) serialize your object to a string and store it in a `"string"` field, then parse it in your app logic. See the [database extension docs](https://better-auth.com/docs/concepts/database) for examples. For the `verifyApiKey` TypeScript error: the correct usage is `auth.apiKey.verifyApiKey`, not `auth.api.verifyApiKey`. The plugin APIs are namespaced, so make sure you're calling the method from the right place. If you still see type errors, double-check that the `apiKey` plugin is enabled in your config and that your types are up to date.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6ab581c0-d323-4c97-bae3-1d8f483a6b2e?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3602)

GiteaMirror commented

2026-04-13 05:16:20 -05:00

@eaoliver commented on GitHub (Jul 25, 2025):

@dosu, so you admit to hallucinating? ;-)

@eaoliver commented on GitHub (Jul 25, 2025): @dosu, so you admit to hallucinating? ;-)

GiteaMirror commented

2026-04-13 05:16:20 -05:00

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

Guilty as charged! 😅 I based that suggestion on the general pattern in the docs, but the Drizzle adapter doesn't actually support "json" as a type for additionalFields—only "string", "number", "boolean", "date", "number[]", and "string[]" are supported. For now, if you need to store JSON-like data, you'll need to stringify it into a "string" field and parse it in your app logic. Thanks for catching that and keeping me honest!

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Jul 25, 2025):  Guilty as charged! 😅 I based that suggestion on the general pattern in the docs, but the Drizzle adapter doesn't actually support "json" as a type for additionalFields—only "string", "number", "boolean", "date", "number[]", and "string[]" are supported. For now, if you need to store JSON-like data, you'll need to stringify it into a "string" field and parse it in your app logic. Thanks for catching that and keeping me honest!  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d6141788-6272-4b08-bf0f-08da7435919d?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/3602)

GiteaMirror commented

2026-04-13 05:16:21 -05:00

@dlindahl commented on GitHub (Sep 26, 2025):

Would love to have a read key added to databaseHooks so that it was easier to serialize/deserialize outside of app logic.

@dlindahl commented on GitHub (Sep 26, 2025): Would love to have a `read` key added to `databaseHooks` so that it was easier to serialize/deserialize outside of app logic.

Sign in to join this conversation.

Branches Tags

2026-05-22/chore/adopt-agents-md

2026-05-22/refactor/string-case-utils

dependabot/npm_and_yarn/uuid-14.0.0

dependabot/npm_and_yarn/turbo-2.9.14

changeset-release/main

main

2026-05-14/fix/passkey-verify-error-and-claim

dependabot/npm_and_yarn/samlify-2.13.0

dependabot/npm_and_yarn/ws-8.20.1

changeset-release/next

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-519ef7475f

dependabot/github_actions/github-actions-98f3470200

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

2026-05-13/ci/stabilize-docker-startup

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-07/fix/admin-set-password-upsert

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

2026-04-21/fix/oauth-rfc-input-validation

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

claude/slack-update-stripe-docs-consistency-8Sc0w

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-24/fix/update-user-info-on-link

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#9659