MobileRegisterBuyerInput
A buyer registering themselves. The account waits for the seller's approval.
input MobileRegisterBuyerInput {
businessType: BuyerBusinessType
code: String!
companyName: String!
contactCustomFields: JSON
customFields: JSON
department: String
displayName: String
email: String!
firstName: String
lastName: String
name: String!
phone: String
registrationNumber: String
secondaryContactName: String
secondaryContactPhone: String
signInNumber: String
subdomain: String
taxId: String
title: String
whatsapp: String
}
Fields
MobileRegisterBuyerInput.businessType ● BuyerBusinessType enum
Whether the buyer is a business or an individual. Recorded on Partner.metadata.businessType. Nullable because older app builds send none — omitted simply records nothing.
MobileRegisterBuyerInput.code ● String! non-null scalar
The 6-digit code the buyer already verified on the OTP screen, which now comes BEFORE this form. Re-checked server-side here because this mutation is what actually creates the account: without it, registration is callable directly and 'verified email' would be a client-side claim (Foundation Gate 3). Required.
MobileRegisterBuyerInput.companyName ● String! non-null scalar
Company / business name.
MobileRegisterBuyerInput.contactCustomFields ● JSON scalar
Values for the organization's own contact fields shown at signup, for the person signing up, keyed by field key. Only fields buyers may fill in are accepted.
MobileRegisterBuyerInput.customFields ● JSON scalar
Values for the organization's own customer fields shown at signup, keyed by field key. Only fields buyers may fill in are accepted.
MobileRegisterBuyerInput.department ● String scalar
The person's department (e.g. 'Procurement'). Stored on their Contact rows, like title.
MobileRegisterBuyerInput.displayName ● String scalar
The name the company trades under, when sign-up shows it. Omitted: the name.
MobileRegisterBuyerInput.email ● String! non-null scalar
Email address.
MobileRegisterBuyerInput.firstName ● String scalar
Given name. Optional for older builds that send only name; when present it takes precedence over splitting name.
MobileRegisterBuyerInput.lastName ● String scalar
Family name. See firstName.
MobileRegisterBuyerInput.name ● String! non-null scalar
Contact/customer person name.
MobileRegisterBuyerInput.phone ● String scalar
Buyer's mobile number in E.164 form (e.g. +97455551234). Persisted to User.phone. Nullable in the SCHEMA for backward compatibility only — app builds predating this field send nothing, and a required field would fail their signup at GraphQL validation before the resolver runs. Current clients treat it as MANDATORY and gate the Sign Up CTA on it.
MobileRegisterBuyerInput.registrationNumber ● String scalar
The company's registration number, when sign-up shows it.
MobileRegisterBuyerInput.secondaryContactName ● String scalar
A second person to call at the company, when sign-up shows a secondary contact. Needs secondaryContactPhone.
MobileRegisterBuyerInput.secondaryContactPhone ● String scalar
The secondary contact's phone in E.164 form, when sign-up shows a secondary contact. Stored as its own contact.
MobileRegisterBuyerInput.signInNumber ● String scalar
Sign-up with a WhatsApp number: the number the registrant proved with code (E.164 or as typed). When sent, code is the one WhatsApp sent to THIS number instead of an email code, email is the registrant's contact email (required, not verified at sign-up), and the number becomes the account's WhatsApp number and sign-in number. Omit for the email sign-up.
MobileRegisterBuyerInput.subdomain ● String scalar
ARC org subdomain this white-label build is pinned to (Constants.expoConfig.extra.orgSubdomain). Determines which tenant the customer is created under. Optional only for backward-compat / dev fallback (MOBILE_BUYER_ORG_ID).
MobileRegisterBuyerInput.taxId ● String scalar
The company's tax ID (e.g. VAT number), when sign-up shows it.
MobileRegisterBuyerInput.title ● String scalar
The person's job title (e.g. 'Purchasing Manager'). Stored on their Contact rows — there is no title column on User.
MobileRegisterBuyerInput.whatsapp ● String scalar
Buyer's WhatsApp number in E.164 form. Persisted as its own WHATSAPP Contact channel row — there is no WhatsApp column on User. Optional: the form lets it be left blank or copied from the mobile number.
Member Of
mobileRegisterBuyer mutation