LeadPersonalInformation class
Constructors
-
LeadPersonalInformation({String? firstName, String? lastName, String? aliasFirstName, String? aliasLastName, String? email, String? city, State? state, String? workPhone, String? primaryPhone, LeadBestTimeToCall? bestTimeToCall, String? address1, String? address2, DateTime? addressMoveInDate, String? zipcode, int? monthsAtAddress, String? driversLicenseNumber, String? driversLicenseState, String? ipAddress, bool? activeMilitary, bool? militaryVeteran, DateTime? dateOfBirth, EducationLevel? educationLevel, String? ssn, CitizenshipStatus? citizenshipStatus, MaritalStatus? maritalStatus})
-
Returns a new LeadPersonalInformation instance.
Properties
-
activeMilitary
↔ bool?
-
Whether the lead is currently in the military (not a veteran)
getter/setter pair
-
address1
↔ String?
-
Street address (primary address line)
getter/setter pair
-
address2
↔ String?
-
Secondary address line
getter/setter pair
-
addressMoveInDate
↔ DateTime?
-
The date the lead moved into their current address
getter/setter pair
-
aliasFirstName
↔ String?
-
The first name the lead uses as an alias
getter/setter pair
-
aliasLastName
↔ String?
-
The last name the lead uses as an alias
getter/setter pair
-
bestTimeToCall
↔ LeadBestTimeToCall?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
citizenshipStatus
↔ CitizenshipStatus?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
city
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
dateOfBirth
↔ DateTime?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
driversLicenseNumber
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
driversLicenseState
↔ String?
-
State in which the driver's license was issued
getter/setter pair
-
educationLevel
↔ EducationLevel?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
email
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
firstName
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
hashCode
→ int
-
The hash code for this object.
no setteroverride
-
ipAddress
↔ String?
-
IP address
getter/setter pair
-
lastName
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
maritalStatus
↔ MaritalStatus?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
militaryVeteran
↔ bool?
-
Whether the lead is a veteran (should not be used if the lead is active in the military)
getter/setter pair
-
monthsAtAddress
↔ int?
-
Number of months the provided address has been the lead's primary residence
getter/setter pair
-
primaryPhone
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
-
ssn
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
state
↔ State?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
workPhone
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair
-
zipcode
↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
getter/setter pair