LOGIN NAME:

PASSWORD:

:: Web Services :: XWeb1003 :: Documentation (Version 1) ::

LoadApplicationsByRepAndDateRangePaged SOAP Method

DESCRIPTION:

Returns 'paginated' 1003 Loan Application records by a specific Rep Identifier, created within a specific date range, in the reverse chronological order the records were entered into the system. Paginated is the ability to return a specific number of records at a time, similar to how search engines display results (i.e. Google's 10 search results on a page).

PARAMETER(S):

strRepIdentifier - String. Indicates the Rep Identifier for which the data is to be returned.
dtDateStart - Date/Time. Indicates the first inclusive date of the date range.
dtDateEnd - Date/Time. Indicates the last inclusive date of the date range.
intPageNumber - Positive Integer. Indicates the page number for which the data is to be returned.
intPageSize - Positive Integer. The number of records you want displayed on a page.

SOAP HEADERS:

LoginName - String. The "Login Name" you chose during the registration process.
Password - String. Your account's "Password".

NOTE***: SOAP Headers are required for authentication.

RETURNS:

XML String, representing the Mortgage Loan Application records in an account either entered by a specific representative or for a specific representative (the record's <Rep_Identifier> value matches the input parameter's value) within the specific date range requested. To view the validating XSD Schema, please click here (opens in a new window). An example is provided here (opens in a new window) or below:

<Applications Total_Record_Count="6">
 <Application Application_ID="7FA07A3937BE4dcb9117425446810283" 
   Date_Created="2004-12-28T10:21:00">
  <Source_Identifier>Powell01</Source_Identifier>
  <Amount>260000.0000</Amount>
  <Property>
   <Address_1>111 Somewhere St.</Address_1>
   <Address_2></Address_2>
   <City>Los Angeles</City>
   <State>CA</State>
   <Postal_Code>90210</Postal_Code>
   <Country>USA</Country>
  </Property>
  <Purpose>
   <Type>1</Type>
   <Type_Description>Purchase</Type_Description>
  </Purpose>
 </Application>
 <Application Application_ID="A81F0D2CAF5C43bb9061BAFB71DEA653" 
   Date_Created="2004-12-25T10:10:00">
  <Source_Identifier>Simon01</Source_Identifier>
  <Amount>325000.0000</Amount>
  <Property>
   <Address_1>543 Some Rd.</Address_1>
   <Address_2></Address_2>
   <City>Los Angeles</City>
   <State>CA</State>
   <Postal_Code>90210</Postal_Code>
   <Country>USA</Country>
  </Property>
  <Purpose>
   <Type>2</Type>
   <Type_Description>Refinance</Type_Description>
  </Purpose>
 </Application>
 ...
</Applications>

If no records exist for that specific representative within the specified time frame, the <Applications> root node will not contain any child elements and the Total_Record_Count attribute will have a value of 0 (zero). An example is provided below:

<Applications Total_Record_Count="0" />

All non-XML strings returned by this method should be considered errors.

ERROR(S):

If the system encounters an error, the method will return one the following messages instead of the expected XML string:

Error: Unable to authenticate. Your username and/or password are invalid. - authentication errors.
Error: You have not yet registered for this service. - authorization errors.
Error: A database error has occurred. Please try again later. - catastrophic database errors.
Error: System error. Unable to process the request. - catastrophic system errors.

ADDITIONAL SUPPORT RESOURCES:

• Frequently Asked Questions specific to this Web Service
• Developer community supported Online Forum
• "How-to" Implementation Guides