registerUser

Registration of a user. Requires special permission from Fluz to enable. Please contact support to enable this feature if needed.

mutation {
  registerUser(
    firstName: String!
    lastName: String!
    phoneNumber: String!
    regionCode: String!
    emailAddress: String!
    dateOfBirth: String!
    billingAddress: VirtualCardBillingAddressInput!
    acceptCardholderAgreement: Boolean!
    deferSeatAssignment: Boolean
  ): RegisterUserResponse
}

Arguments

Argument	Type	Required	Description
`firstName`	`String!`	Yes	The first name of user for registration.
`lastName`	`String!`	Yes	The last name of user for registration.
`phoneNumber`	`String!`	Yes	The phone number of user for registration.
`regionCode`	`String!`	Yes	The region code of phone number for registration.
`emailAddress`	`String!`	Yes	The email of user for registration.
`dateOfBirth`	`String!`	Yes	The date of birth of user for registration.
`billingAddress`	`VirtualCardBillingAddressInput!`	Yes	Billing address used for the user’s virtual card.
`acceptCardholderAgreement`	`Boolean!`	Yes	Must be `true`. Records the user’s acceptance of the cardholder agreement.
`deferSeatAssignment`	`Boolean`	No	When true, creates user without a rewards-network seat. Seat is assigned later at card redemption.

Returns

RegisterUserResponse — represents the response returned from the registerUser mutation.

Field	Type	Description
`success`	`Boolean`	Whether registration completed.
`userId`	`UUID`	The created user. Absent on failure.
`accountId`	`UUID`	The created account. Absent on failure.
`billingAddressId`	`UUID`	The billing address created for the user. Absent on failure.
`error`	`RegisterUserError`	`message` and `code` describing the failure. Absent on success.

Errors

This mutation does not return GraphQL errors for business failures. Every failure comes back as HTTP 200 with success: false and a populated error object holding message and code. Only authentication-middleware and rate-limit failures are rejected before the resolver runs and surface as HTTP errors.

{
  "data": {
    "registerUser": {
      "success": false,
      "error": {
        "message": "The email address you chose is already in use.",
        "code": "AUTH-0027"
      }
    }
  }
}

Branch on error.code, never on error.message — messages are prose and may be reworded, while codes are stable. The tables below list every code this mutation can return. Error name is the internal name for the code; it is not part of the response, and is shown only so support requests and log lines can be matched up.

Application and credential errors

Nothing was created. These indicate a problem with the calling application or its token, and will recur identically until the application setup changes.

Code	Error name	When	Message
`AUTH-0002`	InvalidCredentials	Called with Basic auth, or the bearer token carries no application	`User registration requires a valid user access (Bearer) token.`
`AUTH-0030`	ApplicationInactive	No application matches the token’s application id	`No application found for appId <appId>.`
`AUTH-0030`	ApplicationInactive	The application exists but is not `ACTIVE`	`Application <appId> is not active (current status: <status>).`
`AUTH-0008`	InvalidUserAccess	The bearer token belongs to a user other than the application’s owning developer	`The provided bearer token does not belong to the developer that owns this application.`
`AUTH-0022`	RegistrationNotAllowed	The application lacks the `can_register_user` capability	`This application is not permitted to register users. Please contact support to enable this capability.`

AUTH-0022 means registration has not been enabled for your application. Contact Fluz support rather than retrying.

Input errors

Nothing was created. Fix the input and call again.

Code	Error name	When	Message
`ARG-0002`	MissingArguments	One or more of `firstName`, `lastName`, `phoneNumber`, `regionCode`, `emailAddress`, `dateOfBirth`, `billingAddress` is empty	`Missing required arguments - emailAddress, dateOfBirth are required.`
`ARG-0001`	InvalidArguments	`acceptCardholderAgreement` is not `true`	`acceptCardholderAgreement must be true`
`ARG-0001`	InvalidArguments	`billingAddress` fails schema validation	`Input validation error: <details>`
`AUTH-0004`	InvalidPhoneNumber	`phoneNumber` is not a valid number for `regionCode`	`Please enter a valid phone number.`
`AUTH-0004`	InvalidPhoneNumber	The number is valid but has no E.164 form	`Unable to format provided phone number.`
`AUTH-0004`	InvalidPhoneNumber	`phoneNumber` could not be parsed at all	`Invalid phone number format.`

The ARG-0002 message lists only the fields that were actually absent, and agrees in number (is required / are required). The ARG-0001 validation message appends the specific field errors, so read message for the detail even though you branch on code.

Conflicts

Nothing was created. The email address or phone number already belongs to a Fluz user.

Code	Error name	When	Message
`AUTH-0027`	RegistrationEmailTaken	`emailAddress` already belongs to a Fluz user	`The email address you chose is already in use.`
`AUTH-0026`	RegistrationPhoneTaken	`phoneNumber` already belongs to a Fluz user	`The phone number you chose is already in use.`

Safe to retry with different values. Neither creates a partial user.

Registration failures

Registration could not be completed. Every case below returns the single code AUTH-0025 (UnsuccessfulRegistration) — the message is what distinguishes them.

When	Message
The duplicate email/phone check could not be completed	`Unable to verify whether the email address or phone number is already in use.`
Account creation failed	`Failed to create a new account for the user.`
User creation failed	`Failed to create the user record.`
Rewards-network seat setup failed	`Failed to create a seat for the new account.`
Registration finished without producing a complete user, account, and seat	`User registration did not complete successfully. Please try again.`
Any other unexpected failure	`Please try again again or contact support.`

AUTH-0025 is retryable, but it does not tell you whether the user was created — some stages run after the user and account already exist. Retry the same call, and treat the outcome as the answer:

Success means registration completed and the returned userId is the user to use.
AUTH-0027 or AUTH-0026 means an earlier attempt already created the user; look it up by email address or phone number instead of registering again.
The same AUTH-0025 message repeating means the failure is not transient. Contact Fluz support and quote the message text — it identifies the stage that failed.

API Reference

Conventions

registerUser

Arguments

Returns

Errors

Application and credential errors

Input errors

Conflicts

Registration failures

​Arguments

​Returns

​Errors

​Application and credential errors

​Input errors

​Conflicts

​Registration failures

Arguments

Returns

Errors

Application and credential errors

Input errors

Conflicts

Registration failures