Skip to main content

UpdateMyProfileInput

Changes to the buyer's own profile.

input UpdateMyProfileInput {
  businessType: String
  companyName: String
  department: String
  email: String!
  firstName: String
  lastName: String
  name: String!
  phone: String
  title: String
  whatsapp: String
}

Fields​

UpdateMyProfileInput.businessType ● String scalar​

BUSINESS | INDIVIDUAL → the Partner.type COLUMN (mirrored onto Partner.metadata.businessType), so a buyer's change is visible to the seller console and vice versa. OMITTED leaves the stored value untouched (older builds send none).

UpdateMyProfileInput.companyName ● String scalar​

The name of the buyer's company.

UpdateMyProfileInput.department ● String scalar​

Department → the person's Contact rows. See title.

UpdateMyProfileInput.email ● String! non-null scalar​

Email address.

UpdateMyProfileInput.firstName ● String scalar​

Given name. Optional for older builds sending only name; takes precedence over splitting name when present.

UpdateMyProfileInput.lastName ● String scalar​

Family name. See firstName.

UpdateMyProfileInput.name ● String! non-null scalar​

The buyer's name.

UpdateMyProfileInput.phone ● String scalar​

Mobile number in E.164 form (e.g. +97455551234) → User.phone. OMITTED leaves the stored number untouched; an explicit empty string CLEARS it. Nullable in the schema so older app builds that send no phone do not blank out a number the buyer already has.

UpdateMyProfileInput.title ● String scalar​

Job title → the person's Contact rows. Omitted leaves it untouched; '' clears it.

UpdateMyProfileInput.whatsapp ● String scalar​

WhatsApp number in E.164 form → the person's WHATSAPP Contact channel row (there is no WhatsApp column on User). Same omitted-vs-empty rule as phone: OMITTED leaves it untouched, an explicit empty string CLEARS the channel.

Member Of​

updateMyProfile mutation