Mobile User (Object)

The user object includes the details of the users who are registered on a particular business.

  • Address of the user

  • Whether or not the user has undergone age verification. Possible Values: true, false. The value is set to true if the user's age is verified; otherwise, it is set to false. The response returns this parameter in sign-in, sign-up, and user update APIs if the age verification is enabled for the business in the Punchh platform. Contact your Punchh representative to update this Punchh platform configuration setting.

  • Anniversary date of the user, in YYYY-MM-DD format

  • Whether the user has an Apple sign-up or not. This will return true for the first time sign-up.

  • Unique ID generated by Apple

  • URL of the user's profile image uploaded to an online file storage system. This will be used for users who signed up using email.

  • Date of birth of the user, in YYYY-MM-DD format

  • City where the user lives

  • The email address used for communication with the user

  • Date/time when the user was created in the system, in ISO 8601 format

  • Unique email address used to identify the user

  • Whether the email address of the user has been verified or not

  • Indicates whether the user signed up using Facebook. This parameter returns true the first time a user signs up using Facebook. For all subsequent logins, it returns a false value.

  • List of the user's favorite locations

  • List of store numbers of the user's favorite locations

  • Facebook ID that identifies the user

  • First name of the user

  • Gender of the user

  • Whether the user has generated a Facebook email or not

  • Last name of the user

  • Whether the user has subscribed to receive marketing emails or not

  • Whether the user has subscribed to marketing push-notifications or not

  • Whether the user has a migrate status or not

  • Whether the user has configured a passcode for gift cards or not

  • Phone number of the user

  • Answers given by the user while filling out the user profile.

  • Referral code of the user

  • Referral URL of the user

  • The secondary email address of the user is configured when a user signs up with Facebook but does not share the email address. The app asks for an alternate email address, which is kept as the secondary_email.

  • Whether the user has subscribed to SMS services or not

  • State where the user lives

  • Whether multiple check-ins are allowed for a user. This is used mostly for testing purposes by developers.

  • Whether the terms and conditions of a business have been accepted by a user or not

  • Salutation as selected by the user

  • Date/time when user was updated in the system, in ISO 8601 format

  • Barcode that identifies the user

  • QR code that identifies the user

  • A unique ID that identifies the user. This smaller code can be converted to a QR code in the app and scanned at some POS systems that do not support longer codes. Alternatively, a user could give this to the POS operator if the POS does not have a scanner.

  • ID that identifies the user

  • The object contains information about the relationship details of a user, for example, spouse and kid information. If the user account does not have relationship details, the API returns an empty user_relations object in the response.

    Properties: 4
  • Mode of verification (available only for a user in awaiting migration state)

  • Zip code where the user lives