Developer Programs

Learn

Docs
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.

Developer Resources

API by Reference > Core Services > Loan Application Register Search > Developer Resources

Details

SoapActionhttp://jackhenry.com/ws/LnAppRgtrSrch
Input NameLnAppRgtrSrch
Output NameLnAppRgtrSrchResponse
Input Namespacehttp://jackhenry.com/jxchange/TPG/2008
Group NameInquiry
ContainerTPG_InquiryMaster.xsd

XML Examples

LnAppRgtrSrch Request

XML
 <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SOAP-ENV:Header>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <LnAppRgtrSrch xmlns="http://jackhenry.com/jxchange/TPG/2008">
      <SrchMsgRqHdr>
        <jXchangeHdr>
          <JxVer/>
          <AuditUsrId></AuditUsrId>
          <AuditWsId></AuditWsId>
          <AuthenUsrId/>
          <ConsumerName/>
          <ConsumerProd/>
          <Ver_1/>
          <jXLogTrackingId>{Insert}</jXLogTrackingId>
          <Ver_2/>
          <InstRtId>011001276</InstRtId>
          <InstEnv>TEST</InstEnv>
          <Ver_3/>
          <BusCorrelId/>
          <Ver_4/>
          <WorkflowCorrelId/>
          <Ver_5/>
          <ValidConsmName>{Insert}</ValidConsmName>
          <ValidConsmProd>{Insert}</ValidConsmProd>
          <Ver_6/>
        </jXchangeHdr>
        <MaxRec>{Insert}</MaxRec>
        <Cursor/>
        <Ver_1/>
        <Ver_2/>
        <Ver_3/>
      </SrchMsgRqHdr>
      <AppStatCode/>
      <LnAppId/>
      <Custom/>
      <Ver_1/>
      <IncXtendElemArray>
        <IncXtendElemInfo>
          <XtendElem/>
          <Ver_1/>
        </IncXtendElemInfo>
        <IncXtendElemInfo>
          <XtendElem/>
          <Ver_1/>
        </IncXtendElemInfo>
      </IncXtendElemArray>
      <Ver_2/>
      <InclNAAppDtType/>
      <Ver_3/>
    </LnAppRgtrSrch>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

LnAppRgtrSrch FAQ

Question: Most of the loan app records returned in LnAppRgtrSrch either have a LnAppRgtrSrch.LnAppRgtrSrchRec.ResLnAppRgtrInfo.LnAcctId that has a value of ‘0’ or such that when you pass it into AcctInq you get back “Account not found”. Is this just a problem with the test data on the DMZ? Should LnAcctId always represent an actual loan account that exists on the core?

Answer: The LnAcctId element actually represents the application number. Typically how this works is when a consumer is requesting a loan they fill out an application. The bank then makes a decision whether to grant the request or not. That is what gets reported for the Home Mortgage Disclosure Act (HMDA), all the information that was provided on the application and what it was for, income amounts etc. and whether it was approved/not approved. If approved then a loan record gets created but if not approved it would not have a loan record created. With that said, it’s a problem with test data on the DMZ. LnAcctId won’t always represent an actual loan account on the core.



Have a Question?

Did this page help you?

Last updated Wed Mar 4 2026