FHA Connection B2G

The FHA Connection Business to Government (FHAC B2G) is a way for a Loan Origination System to send information to the FHA Connection in an automated fashion. For a detailed explanation of FHAC B2G, please see the FHAC B2G Guide.

FHAC B2G uses three Document Type Definitions (DTDs). The primary DTD is the HUD_MISMO document which is derived from the Mortgage Industry Standards Maintenance Organization (MISMO) DTD. The second is a special purpose document to facilitate the return of multiple case references for lookup purposes. FHA Lookup list functions for researching data prior to submitting case information use a separate DTD named FHA_ENTITY.

Any institution requesting access to the servicing B2G test environment must first have an existing production FHAC connection ID.

When designing your client applications you will need to be aware of the following regulations:

As stated in Mortgagee Letters 97-14 and 93-13, each FHA Connection user must obtain their own user ID. User IDs are NOT to be shared. Passwords should never be shared, displayed online or divulged publicly. They should not be given to third parties in telephone conversations, placed on office message boards, or left written on telephone message notes on unattended workstations. Using an FHA Connection user ID assigned to another person falls under the provisions of Title 18, United States Code, section 1030. This law specifies penalties for exceeding authorized access, alteration, damage or destruction of information residing on Federal Computers.

Your client applications will need to be able to collect individual user access credentials to be used when authenticating each connection to B2G functions. All IDs must actually belong to individuals; there are no IDs assigned to services. At no time should any user be able to access a transaction using an ID that does not belong to them.

When you are preparring your software for deployment against the produciton environment you will need a valid FHA Connection ID for the produciton server. If you do not already have a production ID you will need to contact your Application Coordinator (or the application coordinator of one of your clients if you do not directly represent an FHA lender) as we can not authorize access to the production environment through this office.

Please review the detailed layouts for Origination functions and List functions.

Please also see the detailed layouts for Servicing functions.

You can find helpful lists of values on the Value Lookup page.

Your B2G client application will need to post XML documents as the value portion of a name/value pair in the body of the request. The name portion of the name/value pair may not be "request," "xml," "post" or any other common name typicaly associated with http handshaking but is not otherwise restricted.

The connection uses BASIC authentication over a 128 bit https transport. You will need to set the content header to application/x-www-form-urlencoded to ensure that the application server parses your request properly. The result of your request is returned as an XML document. At this level; your client application is acting exactly like a webbrowser posting an HTML form to a server.

You can download examples of client applications and source code to assist in your development efforts.
VB6 client
VB6 source
Java client class
Java simple application class
Java client source
Java simple application example source

The downloads are examples to facilitate your own client application development only; no explicit or implied support in the use or modification for use of these examples is offered.

If you are not familiar with the FHA Insurance business processes we strongly suggest that you partner with an FHA lender for assistance because the assistance we can offer here is primarily technical and will be limited in detail and scope when discussing FHA Insurance business rules.