# Prefilling Lead Data with Mobile SDKs The `prefilledData` object should be structured with any fields you want the user not to have to answer themselves, if you already have that info available. Here is an example of `prefilledData` as a Javascript Object. You may prefill as many of these fields as desired; the only 3 *required* are `firstName`, `lastName`, and `email`. ```jsx { "firstName": "Bob", // required "lastName": "Dylan", // required "email": "bobdylan@gmail.com", // required "loanAmount": 7500, // you can instead use "defaultSliderLoanAmount", if you want to suggest a default loan amount but still allow the user to edit it. // if "loanAmount" is prefilled, "defaultSliderLoanAmount" will be ignored "purpose": "credit_card_refi", "dateOfBirth": new Date("1990-01-01"), "address": { "street": "1600 Pennsylvania Avenue", "city": "Washington", "state": "DC", "zip": "20500" }, "primaryPhone": "2325624852", "creditRating": "good", "propertyStatus": "own_with_mortgage", "educationLevel": "associate", "employmentStatus": "employed", "annualIncome": "20000", "hasDirectDeposit": false, "ssn": "512-54-7862", "bankRoutingNumber": "123456789", "bankAccountNumber": "55555555555" } ``` {% hint style="info" %} **Prefilled values cannot be edited by the user** on the final confirm-details screen (before submitting the form). If the user's info is incorrect (e.g. Address is incorrect outdated), the user should edit the info in your app directly. {% endhint %} ### Example React Native Implementation Here is a sample code snippet of how you might implement the Mobile SDK into your app, with all `prefilledData` fields populated: 
<EngineSdk
    bearer="{your_token}"
    primaryColor=”#11aa34”
    secondaryColor=”#444444”
    prefilledData={
              "firstName": "Bob", // required
              "lastName": "Dylan", // required
              "email": "bobdylan@gmail.com", // required
              "loanAmount": 7500, 
                    // you can instead use "defaultSliderLoanAmount", if you want to suggest a default loan amount but still allow the user to edit it.
                    // if "loanAmount" is prefilled, "defaultSliderLoanAmount" will be ignored
              "purpose": "credit_card_refi",
              "dateOfBirth": new Date("1990-01-01"),
              "address": {
                "street": "1600 Pennsylvania Avenue",
                "city": "Washington",
                "state": "DC",
                "zip": "20500"
              },
              "primaryPhone": "2325624852",
              "creditRating": "good",
              "propertyStatus": "own_with_mortgage",
              "educationLevel": "associate",
              "employmentStatus": "employed",
              "annualIncome": "20000",
              "hasDirectDeposit": false,
              "ssn": "512-54-7862",
              "bankRoutingNumber": "123456789",
              "bankAccountNumber": "55555555555"
            }
    clientTags={ ...optional Client Tags, please see following Client Tag section }
    {...optional Event Handlers, please see Event Handler section}
    />
{% hint style="info" %} For any of these fields, *DO NOT* prefill any fields that are empty or otherwise unavailable. If you do not have info for a particular field available to prefill, omit that field in your `prefilledData`object. {% endhint %} For example, this is **incorrect**: ``` {..."firstName": "Bob", "lastName": "Dylan", "address": {}, ...otherAttributes} // empty address is prefilled, which prevents the user from submitting complete info, and they will not receive offers ``` This is **correct**: ``` {"firstName": "Bob", "lastName": "Dylan", ...otherAttributes} //address is not prefilled, which forces the user to input their address in the UI and will allow them to submit complete info and be considered for offers ``` ### PrefilledData Type Validations The data should follow a type schema, described here in Typescript notation: ```typescript interface PrefilledLeadData { firstName: string; lastName: string; email: string; loanAmount?: number; // whole numbers only defaultSliderLoanAmount?: number | string; // if you want the loan amount slider to default to something other than 5000 but want to allow the user to edit the amount, enter it here purpose?: LoanPurpose; // enum below dateOfBirth?: Date; address?: AddressData; // enum below primaryPhone?: string; // leading 1 is fine, but no "+" or "-" chars allowed phoneConsent?: boolean; ssn?: string; // 9 digits with or without hyphens creditRating?: CreditRating; // enum below propertyStatus?: PropertyStatus; // enum below educationLevel?: EducationLevel; // enum below employmentStatus?: EmploymentStatus; // enum below annualIncome?: AnnualIncomeBracket; // enum below hasDirectDeposit?: boolean; bankRoutingNumber?: string; (must be exactly 9 digits) bankAccountNumber?: string; } interface AddressData { /** Primary street address */ street?: string; /** (Optional) Apartment Suite */ apartment?: string; city?: string; state?: string; // must be a valid 2-letter abbreviation zip?: string; } ``` ### Enums/Accepted Values for Certain Fields Certain fields, although strings, must be within a predetermined list of accepted values. Here are those values: ```tsx type LoanPurpose = "debt_consolidation" | "credit_card_refi" | "home_improvement" | "large_purchases" | "other"; type CreditRating = "excellent" | "good" | "fair" | "poor" | "limited"; type PropertyStatus = "own_with_mortgage" | "rent"; type EducationLevel = "high_school" | "associate" | "bachelors" | "masters" | "other_grad_degree" | "other"; type EmploymentStatus = "employed" | "self_employed" | "not_employed" | "retired" | "military" | "other"; type AnnualIncomeBracket = "20000" | "40000" | "60000" | "100000" | "120000" | "121000"; ``` ### PrefilledData Sanitization Prefilled Data must align with the type validations above, and any fields with an accepted value enum must be within that enum. If you (the partner) prefill user data, and any type/value is invalid, that attribute will be stripped, and the lead will have to enter it again manually. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://even-financial.gitbook.io/developer-center/embeddable-integrations/mobile-sdks/react-native/prefilling-lead-data-with-mobile-sdks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.