CLOSINGCORP

ORDER MANAGEMENT
Title Integration Guide
Release Version 3.12

Title Integration Guide June 18, 2020

Title Integration Guide v3.12
Each request sent or received will be accompanied by an HTTP Basic Auth Header with the user credentials.
See Appendix 4.9 for more information. We will supply a username and password for posting messages to
ClosingCorp QA and Prod and the Title Partner will provide to ClosingCorp a username and password for posting
to their QA and Prod environments.

1. Receiving Messages
To receive messages, a Service must be created to handle these messages and the URL provided to ClosingCorp.
Once configured, the system will send messages in XML format in the content body to the URL specified.

Client IDs will be provided by ClosingCorp.

Below are samples of the events that will be sent.

1.1. Fee Questions Request

<FeeQuestionsRequest>
<Client ID="1" Name="WEST" />
<Branch ID="1" Name="Test Branch" /><!-- will not always be present -->
<Order City="Irvine" State="CA" Zip="92612" LoanPurpose="Refinance">
</Order>
</FeeQuestionsRequest>

Expected Return:
<Questions>
<Question>
<QuestionID>…</QuestionID>
<QuestionType>BOOLEAN | INTEGER | NUMERIC | MONEY | PERCENTAGE |
| DATETIME | DATE</QuestionType>
<Description>…</Description>
<DefaultValue>…</DefaultValue>
</Question>

2|Page
 :
</Questions>

Fees Estimate Request

<FeesEstimateRequest>
<Client ID="1" Name="WEST" />
<Branch ID="1" Name="Test Branch" /><!-- will not always be present -->
<Order ReferenceNo="999999999"
Address1="18200 von karman" City="Irvine"
State="CA" Zip="92612" Units="1"
LoanPurpose="Refinance" LoanType="Conventional"
OccupancyType="Primary" PropertyType="Single Family"
LoanAmount="100000.00" SalesPrice="100000.00"
OriginalLoanAmount="100000.00" UnpaidPrincipalAmount="100000.00"
ProductType="1" (see Appendix 4.1) >
</Order>
<AnsweredQuestions>
<Question QuestionID="" Value="" />
:
</AnsweredQuestions>
</FeesEstimateRequest>

Expected Return:
<FeesEstimate>
<Fee>
<HUDLine>…</HUDLine>
<Description>…</Description>
<Amount>…</Amount>
</Fee>
:
</FeesEstimate>

3|Page
 New Order Event
<NewOrder>
<Client ID="1" Name="WEST" />
<Branch ID="1" Name="Test Branch" /><!-- will not always be present -->
<Order ID="159" ReferenceNo="999999999"
Address1="18200 von karman" City="Irvine"
State="CA" Zip="92612" Units="1"
LoanPurpose="Refinance" LoanType="Conventional"
OccupancyType="Primary" PropertyType="Single Family"
LoanAmount="100000.00" SalesPrice="100000.00"
OriginalLoanAmount="100000.00" UnpaidPrincipalAmount="100000.00"
ProductType="1" (see Appendix 4.1) >
<Borrower LastName="test" FirstName="order" MiddleName=”a”
DaytimePhone="" EveningPhone="" CellPhone="" Email="" Ssn=”” />
<CoBorrower LastName="test" FirstName="order" MiddleName=”a”
DaytimePhone="" EveningPhone="" CellPhone="" Email="" Ssn=”” />
</Order>
</NewOrder>

Expected Return:
<ActionStatus>
<Success>True | False</Success>
<Message>Required if Status is False</Message>
</ActionStatus>

Order Note Added Event

<OrderNoteAdded>
<ID>159</ID>
<Note>Please add another comp.</Note>
<NoteDate>5/10/2017 8:28 AM</NoteDate>
<UserType>Processor</UserType>
<UserName>Aaron Rhoads</UserName>
</OrderNoteAdded>

4|Page
 Expected Return:
<ActionStatus>
<Success>True | False</Success>
<Message>Required if Status is False</Message>
</ActionStatus>

1.5. Document Added Event

<Document FileName=”Test.pdf”>
<ID>159</ID>
<DocumentCategory>Miscellaneous</DocumentCategory> (see Appendix 4.7)
<DocumentData><![CDATA[ … ]]></ DocumentData>
</Document>

Expected Return:
<ActionStatus>
<Success>True | False</Success>
<Message>Required if Status is False</Message>
</ActionStatus>

1.6. Schedule Signing Request

ScheduleSigningRequest>
<ID>159</ID>
<SigningDateTime>2020-06-04T09:00:00+700</SigningDateTime>
<SigningLanguage>English</SigningLanguage>

<LocationCompanyName></LocationCompanyName>
<LocationAddress1></LocationAddress1>
<LocationAddress2></LocationAddress2>
<LocationCity></LocationCity>
<LocationState></LocationState>
<LocationZip></LocationZip>
<LocationCounty></LocationCounty>

<DeliveryAddress1></DeliveryAddress1> (if different than above)

5|Page
 <DeliveryAddress2></DeliveryAddress2>
<DeliveryCity></DeliveryCity>
<DeliveryState></DeliveryState>
<DeliveryZip></DeliveryZip>

<SpecialInstructions>...</SpeicalInstructions> </ScheduleSigningRequest>

Expected Return:
<ActionStatus>
<Success>True | False</Success>
<Message>Required if Status is False</Message>
</ActionStatus>

6|Page
2. Sending Messages
Posting messages is basically a reflection of the events sent to you. The primary difference is that we request
you add the additional Provider node. “Provider” and “Client” both need with an ID attribute while the Name
attribute is optional but preferred. For an example, see below. Messages must be sent with an HTTP Basic Auth
Header. See Appendix 4.9 for more information.

Provider and Client IDs will be provided by ClosingCorp.

In QA you will use the URL https://sit.closingcorpordering.com/api/v3.

In Prod you will use the URL https://westvm.com/api/v3.

2.1. Add a Title Document

The DocumentData element is optional. If not present, then the DocumentID element will be used with the
GetDocument method, described in Section 3.5, to request the document data.

<Document FileName="Test.pdf">
<Provider ID="1" Name="{Your Name}" />
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
<DocumentID>1</DocumentID>
<DocumentCategory>Appraisal</DocumentCategory>
[ <DocumentData><![CDATA[ … ]]></ DocumentData> ]
</Document>

Returns:
<ActionStatus>
<Success>True | False</Success>
</ActionStatus>

2.2. Status Changed

<StatusChanged>
<Provider ID="1" Name="{Your Name}" />
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
<StatusID>47</StatusID> (see Section 4.8)
<StatusDesc>CPL Completed</StatusDesc>
</StatusChanged>

Returns:
<ActionStatus>
<Success>True | False</Success>
7|Page
 </ActionStatus>

2.3. Notify when a Note has been added

<OrderNoteAdded>
<Provider ID="1" Name="{Your Name}" />
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
<Note>Please add another comp.</Note>
<NoteDate>5/10/2017 8:28 AM</NoteDate>
</OrderNoteAdded>

Returns:
<ActionStatus>
<Success>True | False</Success>
</ActionStatus>

2.4. Notify when Title Grade has been generated

<TitleGrade>
<Provider ID="1" Name="{Your Name}" />
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
<Grade>A</Grade>
<Description>Title Grade: A</Description>
</TitleGrade>

Returns:
<ActionStatus>
<Success>True | False</Success>
</ActionStatus>

3. Order Status and Notes

Depending on business requirements, it may be necessary to support real-time view of notes and statuses. This
section describes the methods necessary to support for this behavior.

3.1. Provider Order Status

<OrderStatusRequest>
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
</OrderStatusRequest>

8|Page
Expected Return:
<OrderStatus>
<Product>
<TransactionType>1</TransactionType>
<ProductType>1</ProductType>
</Product>
<Status>
<StatusID>1</StatusID>
<StatusDesc>CPL Completed</StatusDesc>
</Status>
<PolicyNumber />
<SearchNumber />
<SubjectProperty>
<Address1 />
<Address2 />
<City />
<State />
<Zip />
<County />
<Unit />
<Subdivision />
<ParcelID />
<LegalDescription />
<AccessedLandValue />
<AccessedImprovementValue />
<AccessInfo />
</SubjectProperty>
<Loan>
<LienPosition />
<LoanNumber />
<LoanAmount />
<LoanConsideration />
<AdditionalAmount />
<CashOutAmount />
</Loan>
<KeyDates>
<OpenedDate>{MM/dd/yyyy}</OpenedDate>
<EstimatedSettlmenetDate>{MM/dd/yyyy}</EstimatedSettlmenetDate>
<ActualSettlementDate>{MM/dd/yyyy}</AcutalSettlementDate>
<ContractreceivedDate>{MM/dd/yyyy}</ContractReceivedDate>
9|Page
 <ContractCloseDate>{MM/dd/yyyy}</ContractCloseDate>
<DisbursedDate>{MM/dd/yyyy}</DisbursedDate>
<CommitmentTypedDate>{MM/dd/yyyy}</CommitmentTypedDate>
<PolicyTypedDate>{MM/dd/yyyy}</PolicyTypedDate>
<ReceivedSaleNotificationDate>{MM/dd/yyyy}</ReceivedSaleNotificationDate>
</KeyDates>
<Buyers>
<LegalEntity>
<Name />
<BusinessName />
<Address>
<Address1 />
<Address2 />
<City />
<State />
<Zip />
</Address>
<Email />
<HomePhone />
<WorkPhone />
<MobilePhone />
<Fax />
<LegalEntity>
:
</Buyers>
<Sellers>
<LegalEntity>
:
</LegalEntity>
:
</Sellers>
<SalesPrice>{decimal}<SalesPrice>
</OrderStatus>

3.2. Provider Order Notes

<OrderNotesRequest>
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
</OrderNotesRequest>

Expected Return: <OrderNotes>

10 | P a g e
 <OrderNote>
<Note>Please add another comp.</Note>
<NoteDate>5/10/2017 8:28 AM</NoteDate>
<UserType>Processor</UserType>
<UserName>Aaron Rhoads</UserName>
</OrderNote>
:
</OrderNotes>

3.3. Provider Order Tasks

<OrderTasksRequest>
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
</OrderTasksRequest>

Expected Return:
<OrderTasks>
<OrderTask>
<Category>Title</Category>
<Name>Perform Search</Name>
<StartedDate>5/10/2017 8:28 AM</StartedDate>
<StartedBy>Aaron Rhoads</StartedBy>
<CompletedDate>5/10/2017 8:28 AM</CompletedDate>
<CompletedBy>Aaron Rhoads</CompletedBy>
</OrderTask>
:
</OrderTasks>

3.4. Provider Documents

<OrderDocumentsRequest>
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
</OrderDocumentsRequest>

Expected Return:
<Documents>
<Document FileName=”Test.pdf”>
<DocumentID>1</DocumentID>
<DocumentCategory>Miscellaneous</DocumentCategory>
<!-- do not send DocumentData in this response -->
11 | P a g e
 </Document>
:
</Documents>

3.5. Get Document Data

<OrderDocumentRequest>
<Client ID="1" Name="{Client Name}" />
<ID>159</ID>
<DocumentID>1</ DocumentID >
</OrderDocumentRequest>

Expected Return:
<Document FileName=”Test.pdf”>
<DocumentID>1</DocumentID>
<DocumentCategory>Miscellaneous</DocumentCategory>
<DocumentData><![CDATA[ … ]]></ DocumentData>
</Document>

4. Appendix

4.1. Order Fields

Field Comments
LoanNumber
Address1 Subject Property
City
State
Zip
Units
LoanAmount
SalesPrice Populated if LoanPurpose is Purchase
OriginalLoanAmount Populated if LoanPurpose is Refinance
UnpaidPrincipalAmount Populated if LoanPurpose is Refinance
PriorConsiderationDate Populated if LoanPurpose is Refinance, for some states
LoanPurpose See Appendix 4.2
LoanType See Appendix 4.3
AmortizationType See Appendix 4.4
OccupancyType See Appendix 4.5

12 | P a g e
 PropertyType See Appendix 4.6
Subordination
Deed
DeedConsiderationAmount
ProductType
4.2. Loan Purpose
ID Comments
Refinance
Purchase
Reverse
Equity
Other

4.3. Loan Type

ID Comments
Conventional
FHA
VA
USDA

4.4. Amortization Type

Fixed
ARM
Interest Only
HELOC

4.5. Occupancy Type

Primary
Secondary
Investment

4.6. Property Type

ID Comments
Single Family
Condo

13 | P a g e
 Multi-Family

4.7. Document Category

ID Comments
ALTASettlementStatement
ALTASettlementStatement_Final
ALTASettlementStatement_Pre
FinalSettlementStatement
IndemnityAffidavit
LegalAndVesting
LenderTitlePackage
PropertyTypeCertification
Title1003
TitleAbstract
TitleBorrAuth
TitleBorrowerDocs
TitleBorrowerIdentification
TitleChain
TitleCleartoCloseCert
TitleCommitment
TitleCommitmentXml
TitleCPL
TitleCredit
TitleDeed
TitleDisbursementLedger-Final
TitleDisbursementLedger-Initial
TitleEO
TitleFedExLabel
TitleFeeSheet
TitleFundstoClose
TitleGradingSheet
TitleHOIDec
TitleHOIInvoice
TitleHUD

14 | P a g e
TitleInvoice
TitleMisc
TitleMortgageStmt
TitleNotaryConfirmed
TitleOther
TitlePayoffReport
TitlePlatMap
TitlePolicy
TitlePowerOfAttorney
TitlePreHUD
TitlePrivacyPolicy
TitlePropertyTypeCert
TitleRecordedOriginals
TitleSearch
TitleSettlementDataXml
TitleSignedDocs
TitleSignedDocs-PreQC
TitleSigningConfirmation
TitleSubordination
TitleTaxCert
TitleTrustDocuments
TitleUnsignedDocs
TitleVestingCert
TitleWireInstructions
TitleWireInstructionsXml

15 | P a g e
4.8. Status ID / Desc
ID Description Comments
1 Started
2 Completed
17 Title Ordered
18 Title Received
31 Title Cancelled
44 PreHUD Completed
45 Commitment Completed
46 Tax Cert Completed
47 CPL Completed
48 Clear to Close
57 Signed Closing Package
62 Profile Report
67 Wire Instructions
68 Lender Title Package
69 Plat Map
72 Property Report Completed
73 Property Report Plus Completed
75 Disbursement Completed
77 Notary Scheduled
78 HUD Completed
81 Pre-Assigned
82 Signing Scheduled
83 Clear To Fund
84 Signing Complete

16 | P a g e
 85 Title On-Hold
86 Title Resumed
93 Title Completed
94 Closing Completed
95 Policy Completed
100 Signing Confirmed

ClosingCorp Order Management Title Integration Guide May 27, 2020

4.9. Authorization Header

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 as form-data variables, using the parameters
username and password, respectively. This method is acceptable, but not encouraged.

17 | P a g e