CCOM Client Order Integration Guide v2.24
CCOM Client Order Integration Guide v2.24
CCOM Client Order Integration Guide v2.24
Document History........................................................................................................................................................... 4
Document Conventions .................................................................................................................................................. 5
1 Purpose of this iGuide ............................................................................................................................................ 6
1.1 Integration Overview ...................................................................................................................................... 6
1.2 Endpoints ........................................................................................................................................................ 6
1.3 Authorization Header ..................................................................................................................................... 7
2 Order Placement & Management .......................................................................................................................... 7
2.1 Submitting a New Appraisal Order Request ................................................................................................... 7
2.2 Submitting a New Title Order Request ......................................................................................................... 10
2.3 Submitting a New Flood Order Request ....................................................................................................... 11
2.4 Submit a New Order for Allocation Only ...................................................................................................... 12
2.5 Order Status.................................................................................................................................................. 13
2.6 Add Document to Order ............................................................................................................................... 15
2.7 Add Note to Order ........................................................................................................................................ 15
2.8 Appraisal Revision Request .......................................................................................................................... 16
2.9 Update User.................................................................................................................................................. 16
2.10 Cancel Appraisal Order ................................................................................................................................. 17
2.11 Cancel Title Order ......................................................................................................................................... 17
2.12 Order Hold / Resume .................................................................................................................................... 17
2.13 Schedule Signing (Title Only) ........................................................................................................................ 18
2.14 Create USER .................................................................................................................................................. 20
3 Receiving API Notifications ................................................................................................................................... 23
3.1 Order Note Added ........................................................................................................................................ 23
3.2 Status Changed ............................................................................................................................................. 23
3.3 Document Added Event................................................................................................................................ 23
3.4 Receiving XML Data ...................................................................................................................................... 24
4. Appendix ............................................................................................................................................................... 25
4.1 Order Fields .................................................................................................................................................. 25
4.2 Loan Purpose ................................................................................................................................................ 31
4.3 Loan Type ..................................................................................................................................................... 31
4.4 Amortization Type ........................................................................................................................................ 32
4.5 Occupancy Type............................................................................................................................................ 32
4.6 Property Type ............................................................................................................................................... 32
4.7 Document Types ........................................................................................................................................... 33
4.8 Appraisal Products ........................................................................................................................................ 37
4.9 Transaction Types ......................................................................................................................................... 39
4.10 Title Product Types ....................................................................................................................................... 39
4.11 Status ID/Desc .............................................................................................................................................. 39
4.12 Title Workflow .............................................................................................................................................. 42
4.13 Appraisal Workflow ...................................................................................................................................... 44
4.14 Flood Workflow ............................................................................................................................................ 45
DOCUMENT HISTORY
DOCUMENT CONVENTIONS
Optional Items marked optional indicate that an action may or may not be required
by the user. If an item is marked optional the user should read the optional
procedure and follow the instructions as necessary.
Items identified in code font are used to indicate
Code Font
programing code.
Italics The use of italics is used to emphasize a word or phrase to the user.
This document provides the information necessary for ClosingCorp clients to successfully integrate with the
ClosingCorp Order Management (CCOM) service. This document will review the Application Programing Interface
(API) methods and options for exchanging data between Clients and CCOM. The intended audience for this
document is all project stakeholders including the project sponsor, senior leadership, and the project team.
Clients will integrate with ClosingCorp Order Management (CCOM) service to place and receive Title, Appraisal and
Flood orders from their Service Providers. All integration requests sent or received will be accompanied by an HTTP
Basic Auth Header with the user credentials, refer to Section 1.3 for more information. CCOM will supply a
username and password for posting messages to CCOM SIT and Production Environments. Clients will provide to
CCOM a username and password for posting to their SIT and Production Environments.
1.2 ENDPOINTS
TABLE 3: ENDPOINTS
Authentication should be sent via HTTP header. The standard HTTP header for basic authentication uses the key
"Authorization" and a value in the form of: "Basic " + Base64 (username + ":" + password)
For example, if your username was “testun” and your password was “testpw1” then the authentication header
would be:
Authorization: Basic dGVzdHVuOnRlc3RwdzE=
Depending on the language you are using, there are sometimes helper methods to assist with this encoding. If
there is a question about how to generate this header, we can provide sample code in various languages.
Alternatively, the username and password may be sent in the body as form-data variables, using the parameters
username and password, respectively. This method is acceptable, but not encouraged.
An explanation of each API method is detailed in the following sections, as well as a sample request and response.
For an explanation of Data Types, refer to Table 4 Order Fields.
The response for all API methods that create, or update orders contain a success element indicating whether the
call was success. <Success>True | False</Success>.
In the API Methods we have listed {ID}, this represents the Order ID within CCOM.
The NewAppraisal method is used to place a new Appraisal order. If the order is created successfully the
response will contain the CCOM Order ID number. For an explanation of Data Types, refer to Table 4.
Note: Clients with provider allocation configured on their account are not required to send the AMC name. Clients
who wish to select their provider should send the AMC Name in their order request to ensure the order is routed to
their preferred provider.
Submit a New Appraisal Order via a POST request to https://closingcorpordering.com/api/v2/NewAppraisal
Request Body (Content-Type: application/XML):
Sample Request:
<NewOrder>
<Order LoanNumber="LN#"
Address1="Property" City=" City" State="ST" Zip="#####" County="County"
EDisclosureConsentDate="2021-10-20"
IntentToProceedReceivedDate="2021-10-19"
Units="#" Address2="Suite/Apt #"
LoanPurpose="Purchase"
LoanType="Conventional"
FHACaseNo=""
DUCaseFileID=""
OccupancyType="Primary"
PropertyType="Single Family"
LoanAmount="150000.00"
SalesPrice="150000.00"
OriginalLoanAmount="150000.00"
UnpaidPrincipalAmount="150000.00"
EstimatedValue="0"
ContactName="Last, First" ContactDaytimePhone="123-123-5555"
ContactEveningPhone="123-123-6666" ContactCell="123-123-7777"
AMC="AMC Name"
OrderProduct="1004"
OrderFha=""
OrderFha203k=""
OrderUsda=""
OrderIncomeStatement=""
OrderRentSchedule=""
OrderComplexProperty=""
OrderRural=""
OrderRush=""
OrderRenovation=""
LoanOfficerEmail=""
UnderwriterEmail=""
ProcessorEmail=""
CloserEmail=""
OtherUser=""
DueDate="mm/dd/yyyy">
<Branch ID="##" Name="overland park" />
<Borrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" Address1="Property"
City=" City" State="ST" Zip="#####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
</Order>
</NewOrder>
Sample Responses:
<Order>
<Success>true</Success>
<ID>38441</ID>
</Order>
<Order>
<Success>false</Success>
<Message>Duplicate Order</Message>
</Order>
The NewTitle method is used to place a new Title order. If the order is created successfully the response will
contain the CCOM ID number. For an explanation of Data Types, refer to Table 4.
Note: Clients with provider allocation configured on their account are not required to send the provider ID. Client
who wish to select their provider should send the Provider ID in their order request to ensure the order is routed to
their preferred provider.
Submitting a New Title Order via a POST request to https://closingcorpordering.com/api/v2/NewTitle
Request Body (Content-Type: application/XML):
Sample Request:
<NewOrder>
<Order LoanNumber="LN#"
Address1="Property"
City="City"
State="ST"
Zip="#####"
County="County"
Units="#"
Address2="Suite/Apt #"
Cema="True|False"
ConstructionToPerm="True|False"
LoanPurpose="Refinance"
TransactionType="Refinance"
LoanType="Conventional"
OccupancyType="Primary"
AmortizationType="Fixed"
PropertyType=" Cooperative"
LoanAmount="150000.00"
EstimatedValue="0"
SalesPrice="150000.00"
OriginalLoanAmount="25000"
TitleProvider="Provider Name"
ProductType="Title and Closing"
PriorDate="mm/dd/yyyy"
UnpaidPrincipalBalance=""
Subordination="True|False"
Deed="True|False"
RequestDeed="True|False"
DeedConsiderationAmount="150000"
LoanOfficerEmail="email@closing.com"
UnderwriterEmail=""
ProcessorEmail=""
CloserEmail=""
OtherUser="" >
<Branch ID="##" Name="Branch Name" />
<Borrower LastName="Last" FirstName="First" MiddleName="a"
DaytimePhone="123-123-1234" EveningPhone="(123) 123-1234"
CellPhone="1231231234" Email="" Ssn="###-##-####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="###-##-####" />
</Order>
</NewOrder>
Sample Responses:
<Order>
<Success>true</Success>
<ID>38441</ID>
</Order>
<Order>
<Success>false</Success>
<Message>Duplicate Order</Message>
</Order>
The NewFlood method is used to place a new Flood order. If the order is created successfully the response will
contain the CCOM ID number. For an explanation of Data Types, refer to Table 4.
Note: Clients with provider allocation configured on their account are not required to send the provider ID. Client
who wish to select their provider should send the Provider ID in their order request to ensure the order is routed to
their preferred provider.
Submit a New Flood Order via a POST request to https://closingcorpordering.com/api/v2/NewFlood
Request Body (Content-Type: application/XML):
Sample Request:
<NewOrder>
<Order LoanNumber="LN#"
Address1="Property" City="City" State="ST" Zip="#####" Units="#"
Address2="Suite/Apt #"
LoanPurpose="Refinance"
LoanType="Conventional"
OccupancyType="Primary"
PropertyType="Single Family"
LoanAmount="150000.00"
SalesPrice="150000.00"
OriginalLoanAmount="150000.00"
UnpaidPrincipalAmount="150000.00" >
<Branch ID="##" Name="overland park" />
<Borrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" />
<CoBorrower LastName="BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" />
</Order>
</NewOrder>
Sample Responses:
<Order>
<Success>true</Success>
<ID>38441</ID>
</Order>
<Order>
<Success>false</Success>
<Message>Duplicate Order</Message>
</Order>
The NewOrder method is used to pre-allocate orders. This method will utilize your provider allocation rules to
assign an order to a provider but not actually send the actual order to provider. You will receive back the Ref ID and
the provider name in the response.
Note: This API should only be used by Lenders who will use provider allocation on CCOM.
Sample Request:
<NewOrder>
<Order LoanNumber="Test 10010"
ReferenceNo="Test 10010"
Address1="address"
City="city"
State="ST"
Zip="#####"
Units="#" >
<Branch ID="##" Name="overland park" />
<Borrower LastName="Last" FirstName="First" MiddleName="a" DaytimePhone="1
23-123-1111" EveningPhone="123-123-2222" CellPhone="123-123-3333"
Email="no@reply.com" Ssn="123-45-6789"/>
<CoBorrower LastName="Co1BorLast" FirstName="BorFirst" MiddleName="M"
DaytimePhone="123-123-1111" EveningPhone="123-123-2222" CellPhone="123-
123-3333" Email="no@reply.com" Ssn="123-45-6789"/>
</Order>
</NewOrder>
Response:
<Order>
<Success>True</Success>
<ID>12345</ID>
<TitleProvider>Provider Name</TitleProvider>
</Order>
The OrderStatus method is used to receive the status and order detail of the Appraisal, Title and/or Flood
orders by Order {ID} number. If the request is submitted successfully the response will provide a list of all statuses
by date and product.
Appraisal, Title and/or Flood: Submit Check Order Status via a POST request to
https://closingcorpordering.com/api/v2/OrderStatus/{ID}?detail=true
Request Body (Content-Type: Application/x-www-form-urlencoded)
Sample Response (will include all statuses and order details generated on the Order ID for all products. If Order ID
is not found or valid, no response will be provided):
The AddDocument method is used to send a document to the Provider on the order. The API expects the CCOM
Order ID and DocType (for Document Type values see in Table 4.7). HTTPS post body must be <100MB.
Add an Order Document via a POST request to
https://closingcorpordering.com/api/v2/AddDocument/{ID}/{DocType}
Request Body (Content-Type: multipart/form-data)
The AddOrderNote method is used to send a note to the Provider on the order. The API expects the CCOM Order
ID and NoteType (Product). The response will contain the Note ID (<Data>) that can be used for tracking the
message.
Add an Order Note via a POST request to
https://closingcorpordering.com/api/v2/AddOrderNote/{ID}
Request Body (Content-Type: application/x-www-form-urlencoded):
noteType={Appraisal | Title}&Subject={NoteSubject}¬e={Note}
Sample Responses:
<ActionStatus>
<Success>true</Success>
<Data>141746</Data>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
<Message>Empty note was not added</Message>
</ActionStatus>
2.8 APPRAISAL REVISION REQUEST
The AddAppraisalRevision method is used to request a revision on the Appraisal order. The API expects the
CCOM Order ID and Revision Request message.
Add an Appraisal Revision Request via a POST request to
https://closingcorpordering.com/api/v2/AddAppraisalRevision/{ID}
Request Body (Content-Type: application/x-www-form-urlencoded):
request={RevisionRequest}
Sample Response:
<ActionStatus>
<Success>true</Success>
<Data>141746</Data>
</ActionStatus>
The UpdateUsers method is used to update or remove a User(s) assigned to an order. The API expects the
CCOM Order ID, User Role, and User email address.
To update or add a User to a Role, POST request to
https://closingcorpordering.com/api/v2/UpdateUsers/{ID}
Sample Responses:
<ActionStatus>
<Success>true</Success>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
<Message>Loan Officer was not found: loanofficer@closing.com</Message>
</ActionStatus>
2.10 CANCEL APPRAISAL ORDER
The AppraisalCancelled method is used to cancel an Appraisal order. This request will be sent to the
provider who will need to confirm the cancelation prior to the order being canceled. Any trip fees or cancelation
fees will need to be resolved and then order can be canceled. The API expects the CCOM Order ID. An optional note
in the Request Body can be sent.
Cancel Appraisal Order via a POST request to https://closingcorpordering.com/api/v2/AppraisalCancelled/{ID}
Request Body (Content-Type: Application/x-www-form-urlencoded):
note={Note}
Sample Response:
<ActionStatus>
<Success>true</Success>
</ActionStatus>
The TitleCancelled method is used to cancel the Title order. Unlike the Appraisal cancelation process, this
request will cancel the Title order on CCOM immediately. CCOM will also send a notification to the Provider
informing them that the Title order has been cancelled. The API expects the CCOM Order ID. An optional note in
the Request Body can be sent.
Cancel Title Order via a POST request to https://closingcorpordering.com/api/v2/TitleCancelled/{ID}
Request Body (Content-Type: Application/x-www-form-urlencoded):
note={Note}
Sample Responses:
<ActionStatus>
<Success>true</Success>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
</ActionStatus>
The Hold/Resume method is used to place an order on hold or resume from a hold status. The API expects the
CCOM Order ID. When hold=true is sent, a holdReason can be sent that specifies the reason for the hold.
Hold/Resume POST request to https:// closingcorpordering.com/api/v2/OrderUpdate/{ID}
Request Body (Content-Type: application/x-www-form-urlencoded):
hold={true|false} & holdReason={message}
Sample Responses:
<ActionStatus>
<Success>True</Success>
<Message>Order is on hold/resumed</Message>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
</ActionStatus>
The Schedule Signing method is used to schedule the closing for your Title order. This will notify the title
agent that you are ready to close this loan and provide the signing information. The API expects the CCOM Order ID
and supports multiple Signing nodes. The Delivery Address nodes are used when the documents need to be
delivered to an address that is different than the address specified in the Location nodes. The
BorrowerIndices attribute specifies which borrowers are associated with each signing location. For dual or
multiple signings, include a Signing node for each signing location and specify which borrowers are associated to
each using BorrowerIndices. To specify more than one borrower for a signing location, use a comma
separated list of values for BorrowerIndices.
Note: An additional parameter, SigningDaylightTime, can be sent in the API call to specify whether daylight savings
or standard. If SigningDaylightTime was sent as True and -6 was sent as SigningTimeZone then OM knows to use
Mountain Daylight Time; if sent as False, then OM knows to use Central Standard Time.
Multiple Signing
<SigningData>
<Signing
SigningDateTime="2020-12-10T09:00:00-700"
SigningTimeZone="-7"
SigningDaylightTime="True"
SigningLanguage="English"
LocationCompanyName="Home"
LocationAddress1="1 Main St"
LocationAddress2="Suite 2"
LocationCity="City"
LocationState="ST"
LocationZip="90210"
LocationCounty="County"
DeliveryAddress1=""
DeliveryAddress2=""
DeliveryCity=""
DeliveryState=""
DeliveryZip=""
SpecialInstructions=""
BorrowerIndices="1,2,3" />
<Signing
SigningDateTime="2020-12-12T09:00:00-700"
SigningTimeZone="-7"
SigningDaylightTime="True"
SigningLanguage="English"
LocationCompanyName="Home"
LocationAddress1="1 Main St"
LocationAddress2="Suite 2"
LocationCity="City"
LocationState="ST"
LocationZip="90210"
LocationCounty="County"
DeliveryAddress1=""
DeliveryAddress2=""
DeliveryCity=""
DeliveryState=""
DeliveryZip=""
SpecialInstructions=""
BorrowerIndices="4,5,6" />
</SigningData>
Sample Responses:
<ActionStatus>
<Success>True</Success>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
<Message></Message>
</ActionStatus>
The CreateUser method is used to create a new user in Order Management for the client making the API call. If
a user exists with a username matching the value of the Email parameter provided, then the user is not created.
HTTP Post Request to: https://closingcorpordering.com/api/v2/CreateUser
Email Alphanumeric
Email address of the user to create. Will also be Required
used as the user’s username.
Role Alpha Order Management role that the new user will Required
belong to. Must be a valid existing role for the
client making the CreateUser call.
SuppressCredential Boolean Specifies whether the newly created user will Required
Email receive an email notifying of the new user
account that was created. If set to True, the user
will not receive an email.
Phone Numeric
Phone Number of the user to create Optional
Branch Alpha Lender Branch that the newly created user will Optional
belong to. If specified, must be a valid existing
Lender Branch.
BrokerName Alpha Name of the Branch that the newly created user Optional
will belong to. If BrokerName or BrokerCode is
specified, Branch will apply to the Broker entity,
and must be a valid existing Broker Branch. Else,
Branch will apply to the Lender entity and must
be a valid existing Lender Branch.
UserName Alphanumeric This is the name the user will use to log into Optional
CCOM Web UI.
Examples:
Sample Response:
<ActionStatus>
<Success>True</Success>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
<Message>User Already Exists</Message>
</ActionStatus>
<ActionStatus>
<Success>false</Success>
<Message>Broker Code Does Not Exist</Message>
</ActionStatus>
3 RECEIVING API NOTIFICATIONS
Clients can receive messages for status updates, notes and documents. In order to receive messages, clients need
to provide CCOM with their API URL endpoint and post back credentials (username and password). The following
notification types are generated by CCOM.
<OrderNoteAdded>
<ID>38425</ID>
<ReferenceNo>Loan/Ref#</ReferenceNo>
<RefID>Provider Order#</RefID>
<NoteID>141747</NoteID>
<Note>Message here</Note>
<NoteDate>05/26/2020 7:44 AM</NoteDate>
<UserType>Account Manager</UserType>
<UserName>User Name</UserName>
</OrderNoteAdded>
Sample Response:
<ActionStatus>
<Success>True | False</Success>
<Message>…if there is an error</Message>
</ActionStatus>
<StatusChanged>
<ID>159</ID>
<ReferenceNo> Loan/Ref #</ReferenceNo>
<RefID>Provider Order#</RefID>
<TypeID>1</TypeID>
<TypeDesc>Appraisal Order</TypeDesc>
<StatusID>2</StatusID>
<StatusDesc>Completed</StatusDesc>
<ChangeDate>11/10/2011 9:43 AM</ChangeDate>
</StatusChanged>
<ActionStatus>
<Success>True | False</Success>
<Message>…if there is an error</Message>
</ActionStatus>
<Document FileName=”Test.pdf”>
<ID>159</ID>
<ReferenceNo>Loan/Ref #</ReferenceNo>
<DocumentID>1</DocumentID>
<DocumentTypeID>1</DocumentTypeID>
<DocumentCategory>Appraisal</DocumentCategory>
<DocumentData><![CDATA[ … ]]></ DocumentData>
</Document>
Sample Response:
<ActionStatus>
<Success>True | False</Success>
<Message>…if there is an error</Message>
</ActionStatus>
XML Data Delivery allows the Lender to receive order specific data for a Title order. The data can be ingested by
the Lender’s Application to update their system and alleviate manual entry of data. The following three XMLs are
the current standardized data formats that a provider will return to the Lender’s system.
3.4.1 TITLE COMMITMENT XML
The following format will be sent to you by your providers.
<Commitment>
<Order ID="149111"/>
<TitleID>328083</TitleID>
<TitleOrderNumber>ABC-123</TitleOrderNumber>
<Vesting>John Doe living trust</Vesting>
<LegalDescription>Lot 55 and block 1234</LegalDescription>
<APN>12-123456789</APN>
<Address>102 S. Main, KATY, TX 77449</Address>
<PropertyType>Recreational (Tennis Club)</PropertyType>
<TitleOrderedDate>11/24/2015</TitleOrderedDate>
<TitleVendorName>Title Agency</TitleVendorName>
<TitleCurrentStatus>In Process</TitleCurrentStatus>
<TitleCurrentStatusDate>11/13/2015</TitleCurrentStatusDate>
<TitleCommitmentCompletedDate>11/13/2015</TitleCommitmentCompletedDate>
<EffectiveDateOfReport>11/13/2015</EffectiveDateOfReport>
</Commitment>
<Settlement>
<Order ID="149111"/>
<Name>Title Agency</Name>
<Address>75 East Fort Union Blvd, C-124</Address>
<City>Midvale</City>
<State>UT</State>
<Zip>84047</Zip>
<NMLSID>DL1234</NMLSID>
<STLicenseID>793886</STLicenseID>
<Contact>John Doe III</Contact>
<ContactNMLSID>78946</ContactNMLSID>
<ContactSTLicenseID>1234567</ContactSTLicenseID>
<Email>titleteam@titleagency.net</Email>
<Phone>(888) 777-6666</Phone>
</Settlement>
3.4.3 TITLE WIRE XML
The following format will be sent to you by your providers.
<WireInstructions>
<Order ID="######"/>
<EscrowNumber>#####</EscrowNumber>
<EscrowCompany>
<Name>Escrow Company Name</Name>
<Address>Escrow Company Street Address</Address>
<City>Escrow Company City</City>
<State>Escrow Company State</State>
<Zip>Escrow Company Zip Code</Zip>
<ContactName>FirstName LastName</ContactName>
<Phone>123-123-1234</Phone>
<Fax>123-123-1234</Fax>
<LicenseNumber>Escrow Company License Number</LicenseNumber>
<ABANumber>ABA Number</ABANumber>
<AccountNumber>Account Number</AccountNumber>
<ForCreditTo>Company Name</ForCreditTo>
<FurtherCredit>Company Name</FurtherCredit>
</EscrowCompany>
<TitleCompany>
<Name>Title Company Name</Name>
<Address>Title Company Street Address</Address>
<City>Title Company City</City>
<State>Title Company State</State>
<Zip>Title Company Zip Code</Zip>
<ContactName>FirstName LastName</ContactName>
<Phone>123-123-1234</Phone>
<Fax>123-123-1234</Fax>
<LicenseNumber>Title Company License Number</LicenseNumber>
<ABANumber>ABA Number</ABANumber>
<AccountNumber>Account Number</AccountNumber>
<ForCreditTo>Company Name</ForCreditTo>
<FurtherCredit>Company Name</FurtherCredit>
</TitleCompany>
</WireInstructions>
4. APPENDIX
Documents Node/
Appraisal/Ti Optional
Element
tle
Borrower Node/
All Required
Element
LastName Attribute Alpha All Required
CoBorrower Node/
All Supports up to five Optional
Element
CoBorrowers
ID NAME COMMENTS
1 Fixed
2 ARM
3 Interest Only
4 Reverse
ID # ID COMMENTS
1 Single Family
Condo
2
3 Multi-Family
4 PUD
5 Manufactured
Please work with your
Cooperative
6 Consultant prior to using.
4.7 DOCUMENT TYPES
LENDER LENDER
ID ID (ENUMERATION) NAME PRODUCT SENDS RECEIVES
11 FloodCert Flood Cert Flood X
110 FloodInvoice Flood Invoice Flood X
15 TripFee TripFee
26 BPO BPO
1 Refinance
2 Purchase
3 Reverse
4 Equity
5 Other
PRODUCTTYPE COMMENTS
Title and Closing This may vary by title provider and transaction type
2 Settlement agent preforms all necessary steps to deliver the title LOS integration endpoint
commitment and other accompanying documents and data xml per receives Document Event
lender specifications. messages for the following
document types:
TitleCommitment,
TitleCommitmentXml,
TitleTaxCert, TitleCPL,
TitleWireInstructions,
TitleWireInstructionsXml,
TitleSettlementDataXml.