CCOM Client Order Integration Guide v2.24

Download as pdf or txt
Download as pdf or txt
You are on page 1of 45

ORDER MANAGEMENT

Client Order Integration Guide


Release Version 2.24

ClosingCorp Order Management ClosingCorp Confidential and Proprietary – Do Not Distribute


Integration iGuide Copyright © 2020
1|P a g e
TABLE OF CONTENTS

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

TABLE 1: DOCUMENT HISTORY


RELEASE DATE OF
AUTHOR DESCRIPTION
VERSION RELEASE
2.12 June 19, 2020 TMorgan Draft – Copied WestVM 2.11 to this new format
2.13 July 23, 2020 TMorgan Section 2.1 and 2.2 - Removed the ability to send documents in the
order request.
Section 2.5 - Removed the ability to send multiple documents in Add
Document request.
Section 4.7 - Updated the Document Type tables
2.14 Aug 14, 2020 TMorgan Section 2.1 and 2.2 – Add County tag in address
2.15 Sept 2, 2020 TMorgan Section 3.3 – Added <DocumentTypeID>1</DocumentTypeID>
and updated <LoanNumber>111111111</LoanNumber>
to <ReferenceNo>Loan/Ref #</ReferenceNo
2.16 Oct 1, 2020 TMorgan/MGilfillan Section 2.1 – Removed OrderNotes and Added DueDate
Section 2.2 – Added PriorDate, UnpaidPrincipalBalance,
Cema, ConstructionToPerm and four additional
<CoBorrower LastName="test" FirstName="order"
MiddleName=”a” DaytimePhone="" EveningPhone=""
CellPhone="" Email="" />
Section 2.4 – Modified OrderStatus to return order details. Added
?detail=true to URL string and updated response with sample.
Section 2.12 – Added Schedule Signing API
Section 3.1-3 – Added Sample Responses
Section 4.6 – Added Cooperative
2.17 Oct 20, 2020 TMorgan Section 1.2 – Added new Scheduling API and updated OrderStatus API
Section 2.1 – Updated sample XML FhaCaseNo to FHACaseNo
Section 2.2 – Added Social Security Number to new coborrowers and
LoanOfficerEmail=""
UnderwriterEmail=""
ProcessorEmail=""
CloserEmail=""
UserEmail=""
Section 2.4 – Updated sample response to add additional borrowers
and Index
Section 2.5 – Updated document size from 37MB to 100MB
Section 2.12 – Added SigningTimeZone=-7 to sample XML and
added BorrowerIndices for multiple signings. Fixed typo in sample
XML Country to County
2.18 Nov. 2, 2020 TMorgan/MGilfillan Section 2.1 & 2.2 – Updated UserEmail to OtherUser in Sample
Section 4.7 – Added 74 TitleFeeSheet and sorted ID’s
Section 4.8 – Updated Appraisal Product Table and added ID
Section 4.11 – Updated all StatusID/Desc Tables by Product
RELEASE DATE OF
AUTHOR DESCRIPTION
VERSION RELEASE
2.19 Feb. 5, 2021 TMorgan/MGilfillan/ Section 1.1 – Removed API Options for JSON
BBailey/HImsirovic Section 2.1 – Added Branch information to the Appraisal order request
Section 2.2 – Added Branch information to the Title order request
Section 2.3 – Added Branch information to the Flood order request
Section 2.4 – Added New Order API
Section 2.4 – Added Branch information to the Allocation request
Section 2.14 – Added CreateUser
Section 3.4 – Added three new XMLs to support Commitment,
Settlement and Wire data being returned to Lender.
Section 4.1 – Updated Borrower address to show as Mailing Address.
Table 16 – Updated to reflect the correct Statuses Sent and received by
the lender.
Table 17 – Updated to reflect the correct Statuses Sent and received by
the lender.
Entire Document - Overall document formatting
2.20 March 24, TMorgan/BBailey Section 2.1 – Added Rush and Rural indicators to XML
2021 Section 2.2 – Updated XML body
Section 2.9 – Added the ability to remove an assigned user from an
order.
Section 2.13 – Added SigningDaylightTime element to XML
Section 3.4.1 -3.4.3 – Updated XML with additional data points.
Table 4 - Added OrderRush and OrderRural values to table
2.21 June 8, 2021 TMorgan Section 2.1 and 2.2 – Removed the verbiage about sending documents.
Section 2.1 – Moved Contact attributes up in XML
Section 2.13 – Added new date point for SigningDaylightTime
Section 3.4.1 – Removed Provider and Client ID
Section 4.1 Table 4 – Added DUCaseFileID, EstimatedValue, Closer and
updated phone number format to ###-###-####
Section 4.8 Table 13 – Added three new products (1004_1007,
1073_10007 and 1004C_1007
2.22 August 12, BBailey Section 2.7 – Added additional API Key to the Note API to support
2021 sending a Subject line with notes.
2.23 Oct. 1, 2021 TMorgan Section 2.1 and Table 2A – Added the ability to send a UserName
Section 4.8 Table 13 – Updated Product Name from 1004P to 1004
Hybrid-Value Verify
2.23.1 Oct. 5, 2021 TMrorgan Section 2.1 – Added Renovation Add-on to order request.
2.24 Oct. 20, 2021 BBailey Section 2.1 – Added eDisclosure Consent Date and Intent to Proceed
Received Date to the order request as a supported elements.

DOCUMENT CONVENTIONS

TABLE 2: DOCUMENT CONVENTIONS


STYLE DESCRIPTION

Bold Bold is used to indicate an action is required by the user.


STYLE DESCRIPTION

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.

1 PURPOSE OF THIS IGUIDE

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.

1.1 INTEGRATION OVERVIEW

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

REQUEST NAME URI - SIT ENVIRONMENT URI – PRODUCTION ENVIRONMENT


Appraisal Order https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Ne
Request NewAppraisal wAppraisal
Title Order Request https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Ne
NewTitle wTitle
Flood Order Request https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Ne
NewFlood wFlood

Order Status https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Ord


OrderStatus/{ID}?detail=true erStatus/{ID}?detail=true
Add Document to https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Add
Order AddDocument/{ID}/{DocType} DocType Document/{ID}/{DocType} DocType Values
Values
REQUEST NAME URI - SIT ENVIRONMENT URI – PRODUCTION ENVIRONMENT
Add Note to Order https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Add
AddOrderNote/{ID} OrderNote/{ID}
Appraisal Revision https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Add
Request AddAppraisalRevision/{ID} AppraisalRevision/{ID}
Update Post User https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/Upd
UpdateUsers/{ID} ateUsers/{ID}
Cancel Appraisal https://sit.closingcorpordering.com/api/v2/ https://closingcorpordering.com/api/v2/App
Order AppraisalCancelled/{ID} raisalCancelled/{ID}
Cancel Title Order https://closingcorpordering.com/api/v2/Titl https://closingcorpordering.com/api/v2/Title
eCancelled/{ID} Cancelled/{ID}
Schedule Signing https://closingcorpordering.com/api/v2/Sc https://closingcorpordering.com/api/v2/Sch
(Title Only) heduleSigning/{id} eduleSigning/{id}

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

2 ORDER PLACEMENT & MANAGEMENT

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.

2.1 SUBMITTING A NEW APPRAISAL ORDER REQUEST

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>

2.2 SUBMITTING A NEW TITLE ORDER REQUEST

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>

2.3 SUBMITTING A NEW FLOOD ORDER REQUEST

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>

2.4 SUBMIT A NEW ORDER FOR ALLOCATION ONLY

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.

Submit a New Order via a POST request to:


https://closingcorpordering.com/api/v2/NewOrder?preAssignAMC={true|false}&preAssignTitle={true|false}
Request Body (Content-Type: application/xml):

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>

2.5 ORDER STATUS

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):

<Order ID="12345" ReferenceNo="Test Order Status" OrderedBy="User@closing.com">


<Borrower LastName="Last" FirstName="First" MiddleName="a" Index="1" />
<CoBorrower LastName="Co1BorLast" FirstName="BorFirst" MiddleName="M"
Index="2" />
<CoBorrower LastName="Co2BorLast" FirstName="BorFirst" MiddleName="M"
Index="3" />
<CoBorrower LastName="Co3BorLast" FirstName="BorFirst" MiddleName="M"
Index="4" />
<CoBorrower LastName="Co4BorLast" FirstName="BorFirst" MiddleName="M"
Index="5" />
<CoBorrower LastName="Co5BorLast" FirstName="BorFirst" MiddleName="M"
Index="6" /> <OrderProperty Address1="1 Order Status Drive" City="BEVERLY
HILLS" State="CA" Zip="90210" />
<AppraisalOrder OrderProduct="1004"
OrderFha="False"
OrderUsda="False"
OrderRentSchedule="False"
OrderIncomeStatement="False"
AMC="Test AMC" ReferenceNo="">
<StatusHistory>
<Status StatusID="1" StatusDate="10/15/2020 8:56 AM">
Started
</Status>
<Status StatusID="3" StatusDate="10/15/2020 8:56 AM">
Order Received
</Status>
<Status StatusID="87" StatusDate="10/15/2020 8:56 AM">
AMC Assigned
</Status>
<Status StatusID="-1" StatusDate="01/01/0001 12:00 AM">
Pending AMC Acceptance
</Status>
</StatusHistory>
</AppraisalOrder>
<FloodOrder ReferenceNo="1209927372">
<StatusHistory>
<Status StatusID="1" StatusDate="10/15/2020 8:56 AM">
Started
</Status>
<Status StatusID="12" StatusDate="10/15/2020 8:56 AM">
Flood Cert Ordered
</Status>
<Status StatusID="34" StatusDate="10/15/2020 8:56 AM">
In Research
</Status>
</StatusHistory>
</FloodOrder>
<TitleOrder LoanAmount="1500000"
SalesPrice="0"
UnpaidPrincipalAmount="1500000"
OriginalLoanAmount="1500000"
PriorConsiderationDate=""
Deed="True"
DeedConsiderationAmount="1500000"
OrderIsCashOut="False"
OrderIsARM="False"
OrderIsSubordinate="False"
TitleProvider="Test Provider"
ReferenceNo="12345">
<StatusHistory>
<Status StatusID="1" StatusDate="10/15/2020 8:57 AM">
Started
</Status>
<Status StatusID="17" StatusDate="10/15/2020 8:57 AM">
Title Ordered
</Status>
<Status StatusID="44" StatusDate="10/15/2020 8:57 AM">
PreHUD Completed
</Status>
<Status StatusID="82" StatusDate="10/16/2020 9:09 AM">
Signing Scheduled
</Status>
</StatusHistory>
</TitleOrder>
</Order>

2.6 ADD DOCUMENT TO ORDER

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)

Sample Successful Response:


<Document>
<Success>true</Success>
<Message>Document ‘Document Name’ was added</Message>
</Document>

Sample Unsuccessful Response:


<Document>
<Success>false</Success>
<Message>Document 'Document Name' was not added</Message>
</Document>

2.7 ADD NOTE TO ORDER

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}&note={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>

2.9 UPDATE USER

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}

To remove a User from a Role, POST request to


https://closingcorpordering.com/api/v2/UpdateUsers/{ID}?allowUnassign=true
Note: When using the remove a user API you must resend all users you want to remain on the order. If any Roles
are missing or left blank the current User assigned to that Role will be remove. The only User that can’t be
removed is the “User” Role.

Request Body, User Roles (Content-Type: application/x-www-form-urlencoded):


LoanOfficer={email}&Processor={email}&Closer={email}&Underwriter={email}&
User={email}

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>

2.11 CANCEL TITLE ORDER

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>

2.12 ORDER HOLD / RESUME

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>

2.13 SCHEDULE SIGNING (TITLE ONLY)

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.

As an example, based on what the user selects in your UI:


(UTC -6:00) Mountain Daylight Time – send SigningDaylightTime="True"
(UTC -6:00) Central Standard Time - send SigningDaylightTime="False”

HTTP POST request to https://closingcorpordering.com/api/v2/ScheduleSigning/{id}


Request Body (Content-Type: application/XML):
Sample Request:
Single 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="" />
</SigningData>

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>

2.14 CREATE USER

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

Request Body (Content-Type: application/x-www-form-urlencoded):


FirstName={UserFirstName}&LastName={UserLastName}&Email={UserEmail}&UserName={User
Name}&Role={UserRole}&SuppressCredentialEmail={SuppressEmail}&Phone={UserPhoneNumber}Branch={UserBra
nchName}&BrokerName={BrokerName}&BrokerCode={UserBrokerCode}
TABLE 2A: PARAMETERS
Parameter DATA TYPE COMMENTS REQUIRED/
OPTIONAL
FirstName Alpha
First name of the user to create Required

LastName Alpha Last name of the user to create Required

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.

BrokerCode Alpha Code that represents a Lender’s Broker entity Optional


that the newly created user will belong to. If
specified, must be a valid existing Lender Broker
entity Code. Note: If specified, a Broker should
not be specified

UserName Alphanumeric This is the name the user will use to log into Optional
CCOM Web UI.
Examples:

Create a new user belonging to Branch2:


HTTP Post Request to: https://closingcorpordering.com/api/v2/CreateUser
Request Body (Content-Type: application/x-www-form-urlencoded):
FirstName={UserFirstName}&LastName={UserLastName}&Email={UserEmail}&UserName={User
Name}&Role={UserRole}&SuppressCredentialEmail={SuppressEmail}&Phone={UserPhoneNumber}&Branch={Branc
h2}

Create a new user belonging to BestBroker:


HTTP Post Request to: https://closingcorpordering.com/api/v2/CreateUser
Request Body (Content-Type: application/x-www-form-urlencoded):
FirstName={UserFirstName}&LastName={UserLastName}&Email={UserEmail}&UserName={User
Name}&Role={UserRole}&SuppressCredentialEmail={SuppressEmail}&Phone={UserPhoneNumber}Branch={UserBra
nchName}&BrokerName={BrokerName}

Create a new user belonging to BrokerCode 123456:


HTTP Post Request to: https://closingcorpordering.com/api/v2/CreateUser
Request Body (Content-Type: application/x-www-form-urlencoded):
FirstName={UserFirstName}&LastName={UserLastName}&Email={UserEmail}&UserName={User
Name}&Role={UserRole}&SuppressCredentialEmail={SuppressEmail}&Phone={UserPhoneNumber}&BrokerCode={Br
oker=12346}

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.

3.1 ORDER NOTE ADDED

<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>

3.2 STATUS CHANGED

<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>

3.3 DOCUMENT ADDED EVENT

<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>

3.4 RECEIVING XML DATA

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>

3.4.2 TITLE SETTLEMENT XML


The following format will be sent to you by your providers.

<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

4.1 ORDER FIELDS

TABLE 4: ORDER FIELDS


FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
Order Node/
All Required
Element
LoanNumber Attribute Alphanumeric All Required

Address1 Attribute Alphanumeric All Subject Property Required


FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
City Attribute Alphanumeric All Subject Property Required

State Attribute Alphanumeric All Subject Property Required

Zip Attribute Alphanumeric All Subject Property Required

Units Attribute Alphanumeric All Subject Property Optional

County Attribute Alphanumeric All Subject Property Optional

Address2 Attribute Alphanumeric All Suite # Optional

CEMA Attribute Boolean Title True or False Optional

ConstructionToPe Attribute Boolean Title True or False Optional


rm

LoanAmount Attribute Numeric Title Title and Appraisal Required only


supports for Title

ContactName Attribute Alpha Appraisal "Last, First" Optional

ContactDay Attribute Numeric Appraisal ###-###-#### Optional


TimePhone

Contact Attribute Numeric Appraisal ###-###-#### Optional


EveningPhone

ContactCell Attribute Numeric Appraisal ###-###-#### Optional


LoanOfficerEmail
Attribute Email All Email - User needs Optional
to be configured
prior to sending.

UnderwriterEmail Attribute Email All Email - User needs Optional


to be configured
prior to sending.

ProcessorEmail Attribute Email All Email - User needs Optional


to be configured
prior to sending.

CloserEmail Attribute Email All Email - User needs Optional


to be configured
prior to sending.

OtherUser Attribute Email All Email - User needs Optional


to be configured
prior to sending.
FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
OrderIncome Attribute Boolean Appraisal Add Ons for Optional
Statement Appraisal - True or
False

OrderRent Attribute Boolean Appraisal Add Ons for Optional


Schedule Appraisal - True or
False

OrderComplex Attribute Boolean Appraisal Add Ons for Optional


Property Appraisal - True or
False

OrderFha Attribute Boolean Appraisal Add Ons for Optional


Appraisal - True or
False

OrderFha203k Attribute Boolean Appraisal Add Ons for Optional


Appraisal - True or
False

OrderUsda Attribute Boolean Appraisal Add Ons for Optional


Appraisal - True or
False

OrderRural Attribute Boolean Appraisal Add Ons for Optional


Appraisal - True or
False

OrderRush Attribute Boolean Appraisal Add Ons for Optional


Appraisal - True or
False

FHACaseNo Attribute Numeric Appraisal e.g. 123-4567890 Required if


LoanType is FHA
- 10-digits

DUCaseFileID Attribute Numeric Appraisal Optional

SalesPrice Attribute Numeric Title Required if


LoanPurpose is
Purchase

OrigLoan Attribute Numeric Title Required if


Amount LoanPurpose is
Refinance
FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
Unpaid Attribute Numeric Title Required if
Principal LoanPurpose is
Balance Refinance
Estimated
Value Attribute Numeric Title and Optional
Appraisal

PriorDate Attribute Date Title MM/DD/YYYY Required if


LoanPurpose is
Refinance

EDisclosure Attribute Date All MM/DD/YYYY Optional


ConsentDate

IntentTo Attribute Date All MM/DD/YYYY Optional


Proceed
ReceivedDate

LoanPurpose Attribute Enumeration All Required - See


Appendix X

Transaction Attribute Enumeration Title The values Required


Type available are
determined by the
provider
TransactionType
Mappings

LoanType Attribute Enumeration All See Appendix X Required

AmortizationType Attribute Enumeration All See Appendix X Required

Occupancy Attribute Enumeration All See Appendix X Required


Type

PropertyType Attribute Enumeration All See Appendix X Required

OrderProduct Attribute Enumeration Appraisal See Appendix X Required -


Appraisal Only

ProductType Attribute Enumeration Title See Appendix X Required - Title


Only

IsARM Attribute Boolean Appraisal True or False Optional

IsFHA Attribute Boolean Appraisal True or False Optional

Is Attribute Boolean Appraisal True or False Optional


Manufactured
FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
IsCashOut Attribute Boolean Title True or False Optional

IsInTrust Attribute Boolean Title True or False Optional

Is Attribute Boolean Title True or False Optional


Subordination

Subordinate Attribute Alphanumeric Title Send Subordinate Required when


To Lender IsSubordination
is True.

Deed Attribute Boolean Title True or False Optional

Deed Attribute Numeric Title Required when


Consideration Deed is True.
Amount

AMC Attribute Alphanumeric Appraisal Send Provider Required if


Name lender is not
using auto
allocation. If
sent, this will
override
allocations

Title Attribute Alphanumeric Title Send Provider Required if


Provider Name lender is not
using auto
allocation. If
sent, this will
override
allocations

TitleBranch Attribute Alphanumeric Title Optional

OrderNotes Attribute Alphanumeric Appraisal/Ti Optional


tle

Institution Attribute Alphanumeric All Optional

Documents Node/
Appraisal/Ti Optional
Element
tle

Document Element Appraisal/Ti Optional


tle

FileName Attribute Alphanumeric Appraisal/Ti Optional


tle
FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
Document Element Enumeration Appraisal/Ti Optional
Category tle

DocumentData Element <![CDATA[ … Appraisal/Ti Base64 Encoded Optional


]]> tle

Borrower Node/
All Required
Element
LastName Attribute Alpha All Required

FirstName Attribute Alpha All Required

MiddleName Attribute Alpha All Optional

DaytimePhone Attribute Numeric All ###-###-#### Optional

EveningPhone Attribute Numeric All ###-###-#### Optional

CellPhone Attribute Numeric All ###-###-#### Optional

Email Attribute Alphanumeric All Required for


Appraisal if
electronic
delivery of
appraisal.pdf to
borrower is
required

Ssn Attribute Alphanumeric All ###-##-#### Required for


Title

Address1 Attribute Alphanumeric All Mailing Address Required

City Attribute Alphanumeric All Mailing Address Required

State Attribute Alphanumeric All Mailing Address Required

Zip Attribute Alphanumeric All Mailing Address Required

Address2 Attribute Alphanumeric All Suite # Optional

CoBorrower Node/
All Supports up to five Optional
Element
CoBorrowers

LastName Attribute Alpha All Optional

FirstName Attribute Alpha All Optional

MiddleName Attribute Alpha All Optional


FIELD ITEM TYPE DATA TYPE PRODUCT COMMENTS REQUIRED/
OPTIONAL
DaytimePhone Attribute Numeric All ###-###-#### Optional

EveningPhone Attribute Numeric All ###-###-#### Optional

CellPhone Attribute Numeric All ###-###-#### Optional

Email Attribute Alphanumeric All Optional

Ssn Attribute Alphanumeric All ###-##-#### Optional

4.2 LOAN PURPOSE

TABLE 5: LOAN PURPOSE


ID NAME COMMENTS
1 Refinance
2 Purchase Default if not sent
3 Reverse
4 Equity
5 Other

4.3 LOAN TYPE

TABLE 6: LOAN TYPE


ID NAME COMMENTS
1 Conventional
2 FHA Requires "FHACaseNo”
3 VA
4 USDA
5 FHA 203K
6 Jumbo
7 NonConforming
8 HELOC
4.4 AMORTIZATION TYPE

TABLE 7: AMORTIZATION TYPE

ID NAME COMMENTS

1 Fixed
2 ARM
3 Interest Only
4 Reverse

4.5 OCCUPANCY TYPE

TABLE 8: OCCUPANCY TYPE


ID NAME COMMENTS
1 Primary
2 Secondary
3 Investment

4.6 PROPERTY TYPE

TABLE 9: PROPERTY TYPE

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

TABLE 10: TITLE DOCUMENT TYPE


ID ID (ENUMERATION) NAME PRODUCT LENDER LENDER
SENDS RECEIVES
15 TitlePreHud Title Pre-HUD Title X
16 TitleCommitment Title Commitment Title X
17 TitleTaxCert Title Tax Certificate Title X
18 TitleCpl Title Closing Protection Title X
Letter (Cpl)
19 TitleDeed Title Deed Title X
20 TitleOther Title Other Title X
21 TitlePayoffReport Title Payoff Report Title X
22 TitleUnsignedDocs Title Unsigned Documents Title X
23 TitleHud Title HUD Title X
24 TitleFedEXLabel Title FedEX Label Title X
27 Title1003 Title 1003 Title X
28 TitleCredit Title Credit Title X

29 TitleEO Title Errors and Omissions Title X


(EO)
30 TitleHoiDec Title Homeowners Insurance Title X
Declarations Page
31 TitleBorrAuth Title Borrower Authorization Title X
36 TitleSignedDocs Title Signed Docs Title X
37 TitleMortgageStmt Title Mortgage Statement Title X
38 ProfileReport Profile Report Title X
45 TitleSignedDocsPreQC Title Signed Docs Pre-QC Title X
46 TitleCancelFile Title Cancel File Title X
47 TitleWireInstructions Title Wire Instructions Title X
48 LenderTitlePackage Lender Title Package Title X
49 TitlePlatMap Title Plat Map Title X
51 TitleBorrower Title Borrower Identification Title X
Identification
52 TitleHoiInvoice Title Homeowners Insurance Title X
Invoice
54 PropertyReport Property Report Title X
55 PropertyReportPlus Property Report Plus Title X
ID ID (ENUMERATION) NAME PRODUCT LENDER LENDER
SENDS RECEIVES
59 TitleBorrowerDocs Title Borrower Docs Title X
62 TitleCommitmentXml Title Commitment XML Title X
67 ExpressProperty Express Property Report Title X
Report
68 ExpressProperty Express Property Report Title X
ReportXml XML
70 TitleSettlementData Title Settlement Data XML Title X
Xml
71 TitleInvoice Title Invoice Title X
72 TitleChain Title Chain Title X
73 TitlePrivacyPolicy Title Privacy Policy Title X
74 TitleFeeSheet Title Fee Sheet Title X
75 TitleGradingSheet Title Grading Sheet Title X

77 TitleDisbursement Title Disbursement Ledger Title X


LedgerInitial Initial
78 TitleDisbursement Title Disbursement Ledger Title X
LedgerFinal Final
79 ALTASettlement ALTA Settlement Statement Title X
Statement
80 PropertyType Property Type Certification Title X
Certification
81 TitleSubordination Title Subordination Title X
82 TitleClosingDisclosure TitleClosingDisclosure Title X
83 TitlePolicy Title Policy Title X
84 TitleSearch Title Search Title X
85 TitleAbstract Title Abstract Title X
86 TitleVestingCert Title Vesting Certificate Title X
87 TitleRecordedOriginals Title Recorded Originals Title X
88 TitleNotaryConfirmed Title Notary Confirmed Title X
89 TitleClearToCloseCert Title Clear To Close Title X
Certificate
90 TitleMisc Title Misc Title X
91 TitleFundsToClose Title Funds To Close Title X
92 TitleSigning Title Signing Confirmation Title X
Confirmation
ID ID (ENUMERATION) NAME PRODUCT LENDER LENDER
SENDS RECEIVES
94 TitleTrailingDocs Title Trailing Documents Title X

95 ALTASettlement ALTA Settlement Statement Title X


Statement_Final2 Final 2
96 ALTASettlement ALTA Settlement Statement Title X
Statement2 2
98 TitlePowerOfAttorney Title Power Of Attorney Title X
99 TitlePropertyTypeCert Title Property Type Cert Title X
100 TitleTrustDocuments Title Trust Documents Title X
101 LegalAndVesting Legal And Vesting Title X
102 IndemnityAffidavit Indemnity Affidavit Title X
103 FinalSettlement Final Settlement Statement Title X
Statement
104 TitleWireInstructions Title Wire Instructions XML Title X
Xml
105 TitleRequestInfo Title Request Info Title X
106 ExternalTitleProvider External Title Provider Order Title X
OrderEmail Email
115 TitleOrderDocs Title Order Docs Title X
116 TitleCommitment2 Title Commitment 2 Title X
117 TitleCpl2 Title Closing Protection Title X
Letter (Cpl) 2
118 TitleSignedDocs2 Title Signed Docs 2 Title X
119 TitleSignedDocsPreQC2 Title Signed Docs Pre-QC 2 Title X
120 LenderTitlePackage2 Lender Title Package 2 Title X

121 TitleDisbursement Title Disbursement Ledger Title X


LedgerInitial2 Initial 2
122 TitleDisbursement Title Disbursement Ledger Title X
LedgerFinal2 Final 2
123 ALTASettlement ALTA Settlement Statement Title X
Statement_Pre2 Pre 2
124 TitlePolicy2 Title Policy 2 Title X
125 TitleRecordedOriginals Title Recorded Originals 2 Title X
2
126 ALTASettlement ALTA Settlement Statement Title X
Statement_Pre Pre
ID ID (ENUMERATION) NAME PRODUCT LENDER LENDER
SENDS RECEIVES
127 ALTASettlement ALTA Settlement Statement Title X
Statement_Final Final
128 TitleCoverPage Title Cover Page Title X
129 TitleAdditionalDocs Title Additional Docs Title X
130 TitleJudgements Title Judgements Title X
131 TitleRelease_ Title Release Conveyance Title X
Conveyance

TABLE 11: APPRAISAL DOCUMENT TYPE


LENDER LENDER
ID ID (ENUMERATION) NAME PRODUCT SENDS RECEIVES
1 Appraisal Appraisal Appraisal X
2 License License Appraisal X
5 EO Errors and Omissions Appraisal X
12 AppraiserInvoice Appraiser Invoice Appraisal X
25 ConditionReport Condition Report Appraisal X
32 AppraisalXml Appraisal XML Appraisal X
33 Invoice Invoice Appraisal X
Fannie Mae Successful Submission
34 FannieMaeSsr Report (SSR) Appraisal X
Freddie Mac Successful Submission
35 FreddieMacSsr Report (SSR) Appraisal X
40 AppraisalCopyEmail Appraisal Copy Email Appraisal X
AppraisalReview
53 Report Appraisal Review Report Appraisal X
57 FeesEstimate Fees Estimate Appraisal X
FieldReviewPrior
58 Appraisal Field Review Prior Appraisal Appraisal X
63 AppraisalInspections Appraisal Inspection Appraisal X
64 AppraisalReviews Appraisal Reviews Appraisal X
66 AppraisalCopyLetter Appraisal Copy Letter Appraisal X
CertificateOf
69 Compliance Certificate Of Compliance Appraisal X
76 FhaSsr FHA Successful Submission Report (SSR) Appraisal X
107 AppraisalBPO Appraisal BPO Appraisal X
LENDER LENDER
ID ID (ENUMERATION) NAME PRODUCT SENDS RECEIVES
108 InvoiceBPO Invoice BPO Appraisal X
109 InvoiceInspections Invoice Inspections Appraisal X
111 AppraisalFNMA Appraisal FNMA Appraisal X
112 InvoiceFNMA Invoice FNMA Appraisal X
113 Appraisal1004P Appraisal 1004P Appraisal X
114 Invoice1004P Invoice 1004P Appraisal X
41 VIReport VI Report Appraisal X
42 VIReportXml VI Report XML Appraisal X
LoanSafe Appraisal Management (LSMR)
43 LSAMReport Report Appraisal X
44 FNCReport FNC Report Appraisal X
93 FNCCMSReport FNC CMS Report Appraisal X
3 PurchaseAgreement Purchase Agreement Appraisal X
4 AppraisalMisc Appraisal Misc Appraisal X

TABLE 12: FLOOD DOCUMENT TYPE

LENDER LENDER
ID ID (ENUMERATION) NAME PRODUCT SENDS RECEIVES
11 FloodCert Flood Cert Flood X
110 FloodInvoice Flood Invoice Flood X

4.8 APPRAISAL PRODUCTS

TABLE 13: APPRAISAL PRODUCTS

ID Enumeration Product Name

1 1004 1004 Single-Family

2 1004DU 1004D Update/Recert.

3 1004DF 1004D Final Inspection

5 1025 1025 Multi-Family 2 Units


ID Enumeration Product Name

6 1073 1073 Condo

7 1075 1075 Ext Only Condo

8 2055 2055 Ext Only SFR

9 2000 2000 Field Review

10 DeskReview Desk Review

11 216 216 Operating Income Stmt

12 1007 1007 Comparable Rent Sched

13 2075 2075 DU Property Report

15 TripFee TripFee

16 ConditionReport Condition Report

18 DisasterExt Disaster Report Ext Only

19 DisasterIntExt Disaster Report Int/Ext

20 1004C 1004 Manufactured Home

21 1025_3U 1025 Multi-Family 3 Units

22 1025_4U 1025 Multi-Family 4 Units

23 92051 HUD 92051 Compliance Inspection

24 FhaC FHA Conversion

25 DesktopValuation Desktop Valuation Inspection

26 BPO BPO

27 1004P 1004 Hybrid-Value Verify

28 FNMAPropertyInspection FNMA Property Inspection

29 2090 2090 Co-op


ID Enumeration Product Name

30 2095 2095 Ext Only Individual Coop

31 1004INV 1004 Investment (w/ 1007)

32 1004CINV 1004C Investment (w/ 1007)

33 1073INV 1073 Investment (w/ 1007)

4.9 TRANSACTION TYPES

TABLE 14: TRANSACTION TYPES


ID TRANTYPE COMMENTS

1 Refinance

2 Purchase

3 Reverse

4 Equity

5 Other

4.10 TITLE PRODUCT TYPES

TABLE 15: TITLE PRODUCT TYPES

PRODUCTTYPE COMMENTS

Title and Closing This may vary by title provider and transaction type

4.11 STATUS ID/DESC

TABLE 16: STATUS ID/DESC - APPRAISAL


ID Status Lender Receives Lender Sends
2 Completed x
3 Order Received x
7 Appraisal Uploaded x
27 Inspection Scheduled x
ID Status Lender Receives Lender Sends
30 Payment Received x
33 Order Cancelled x
35 Partial Payment Refunded x
36 Payment Refunded x
37 Revision Requested
38 Revision Pending x
39 Revision Uploaded x
42 On-Hold x x
43 Order Resumed x x
55 UCDP Successful x
63 Inspection Completed x
64 Copy Sent to Borrower x
74 Borrower's Copy Viewed x
76 Borrower's Copy Mailed x
79 Awaiting Payment x
87 AMC Assigned x
88 AMC Accepted x
89 AMC Cancelled x
90 Payment Approved x
91 Partial Payment Received x
92 Order Cancel Requested x
96 Invoice Updated x
98 AMC Appraiser Assigned x
99 Due Date Updated x x
104 Inspection Cancelled x
106 1004P Required x

TABLE 17: STATUS ID/DESC – TITLE


ID Status Lender Receives Lender Sends
2 Completed x
17 Title Ordered x
18 Title Received x
31 Title Cancelled x
ID Status Lender Receives Lender Sends
44 PreHUD Completed x
45 Commitment Completed x
46 Tax Cert Completed x
47 CPL Completed x
48 Clear to Close x
57 Signed Closing Package x
62 Profile Report x
67 Wire Instructions x
68 Lender Title Package x
69 Plat Map x
72 Property Report Completed x
Property Report Plus
73
Completed x
75 Disbursement Completed x
77 Notary Scheduled x
78 HUD Completed x
81 Pre-Assigned x
82 Signing Scheduled x
83 Clear To Fund x
84 Signing Complete x
85 Title On-Hold x x
86 Title Resumed x x
93 Title Completed x
94 Closing Completed x
95 Policy Completed x
97 Title Recorded Originals x
100 Signing Confirmed x
102 ALTA Settlement - Pre x
103 ALTA Settlement - Final x
105 Title Grade Received x
107 Title Vesting Cert x
TABLE 18: STATUS ID/DESC - FLOOD
ID Status Lender Receives
2 Completed x
12 Flood Cert Ordered x
13 More Information Needed x
14 Flood Cert Received x
34 In Research x
101 Allocated x

4.12 TITLE WORKFLOW

TABLE 18: TITLE WORKFLOW


# STEP EXPECTED RESULTS

1 Title Order Request Settlement agent receives the


title order. Response:
LOS calls https://closingcorpordering.com/api/v2/NewTitle to
Successful and includes
place the title order.
OrderID.

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.

Note: Document types


received dependent upon
lender specifications and
provider integrations.
Payoff/Subordination Requests Settlement agent receives
3
title note to order payoffs or
LOS calls https://closingcorpordering.com/api/v2/AddOrderNote subordinations.
to send an Order Note containing Payoff/Subordination request
information.
4 Settlement agent returns payoff / subordination documentation. LOS integration endpoint
receives Document Event
messages for the following
document types:
# STEP EXPECTED RESULTS
TitleSubordination and
TitlePayoffReport.

5 Settlement agent delivers clear to close status. LOS integration endpoint


receives ClearToClose
StatusChanged message.

Schedule the Signing


6 Settlement agent receives
When the signing is ready to be scheduled, LOS calls
scheduling date, time and
https://closingcorpordering.com/api/v2/AddOrderNote to send
location.
scheduling request and signing information to settlement agent.

7 Settlement agent assigns a notary or closing agent LOS integration endpoint


receives SigningConfirmed
StatusChanged message. LOS
integration endpoint may also
receive
TitleSigningConfirmation
or TitleNotaryConfirmed
Document Event message.
Closing Package Delivery
8 Settlement agent receives
closing package and prepares
LOS calls
for closing with Borrower.
https://qa.closingcorpordering.com/api/v2/AddDocument/{ID}/{DocType}
to deliver the closing package with Doc Type = LenderTitlePackage
Closing/Signing Completed
9 LOS integration endpoint
receives SigningComplete
Settlement agent delivers notification signing has been completed.
StatusChanged message.

Executed Closing Package Delivery


10 LOS integration endpoint
Settlement agent completes the quality control process and delivers the
receives TitleSignedDocs
executed closing package
Document Event message.
Funds Disbursement
11 LOS integration endpoint
receives
Settlement agent disburses funds and delivers the disbursement ledger. TitleDisbursementLedger-
Initial and / or
TitleDisbursementLedger-
Final Document Event
messages
Title Policy Delivery
12 LOS integration endpoint
Settlement Agent delivers final Title Policy.
receives TitlePolicy
Document Event message.

13 Title Order Fulfillment Complete


4.13 APPRAISAL WORKFLOW

TABLE 19: APPRAISAL WORKFLOW


# STEP EXPECTED RESULTS
Appraisal Order Request AMC receives the Appraisal Order.
1
Response: Successful and includes
LOS calls OrderID.
https://closingcorpordering.com/api/v2/NewAppraisal to
place the Appraisal order.
AMC places Appraisal Order on hold pending confirmation of AMC has appraisal on hold
2
payment by borrower. CCOM will generate the email pending receipt of payment.
notification to Borrower/Cardholder with payment link for CCOM delivers email to
credit card. Borrower/Cardholder with link to
Authorize.net for credit card
processing.
Appraisal Payment Processed AMC proceeds with appraiser
3
CCOM will deliver notification of successful credit card assignment and order fulfillment.
payment received to AMC.
Appraiser Assignment and Inspection Scheduling LOS integration endpoint receives
4
AMC will confirm an appraiser has been assigned by delivering AppraiserAssigned
an AppraiserAssigned status. StatusChanged message.
AMC schedules the inspection and delivers LOS integration endpoint receives
5
InspectionScheduled status. InspectionScheduled
StatusChanged message.
On Hold and Resume LOS integration endpoint receives
6
OnHold StatusChanged message.
AMC receives message from Appraiser there is an issue with
access to the property. AMC notifies Lender the order is on
hold pending resolution to access issue.
AMC resolves access issue with Borrower and resumes the LOS integration endpoint receives
7
Appraisal Order. Notification is provided to Lender Appraisal OrderResumed StatusChanged
Order fulfillment has been resumed. message.
Appraisal Delivery LOS integration endpoint receives
8
AppraisalXML and Appraisal
AMC will perform QC on the Appraisal and deliver the Document Event messages.
Appraisal MISMO xml file.
AMC will also deliver the UCDP and EAD SSRs and Appraisal LOS integration endpoint receives
9
Invoice documents. FannieMaeSSR, FreddieMacSSR,
FHASSR and AppraiserInvoice
Document Event messages.
Revision Requests AMC receives revision request and
10
works with Appraiser to make
LOS calls https://closingcorpordering.com/api/v2/ revisions.
AddAppraisalRevision/{ID} with the reference ID of the
original Appraisal Order to request an appraisal revision.
AMC will confirm receipt of revision request by sending an LOS integration endpoint receives
11
Appraisal Note. OrderNoteAdded message.
AMC will deliver the revised Appraisal MISMO xml file and any LOS integration endpoint receives
12
applicable additional documents. revised AppraisalXML and
# STEP EXPECTED RESULTS
Appraisal Document Event
messages. LOS integration
endpoint may also receive revised
FannieMaeSSR, FreddieMacSSR,
FHASSR and AppraiserInvoice
Document Event messages.
Appraisal Delivery to Borrower Borrower receives email and
13
downloads Appraisal.
CCOM will deliver email to Borrower with the link to
download the Appraisal.
Appraisal Order is Complete.
14

4.14 FLOOD WORKFLOW

TABLE 4.14 FLOOD WORKFLOW


# STEP EXPECTED RESULTS
Flood Order Request
1 Flood Provider receives Flood Order.
LOS calls Response: Successful and includes
https://closingcorpordering.com/api/v2/NewFlood to OrderID.
place the Flood order.
2 Flood Delivery LOS integration endpoint receives
Flood MISMO XML and/or FloodCert
Flood Provider delivers Flood MISMO XML. Document Event messages.

3 Flood Order Request is Complete

You might also like