Technical Setup Guide

Setting up a communication between your POS and Snapdocs Connect will enable this seamless experience. Reference our API documentation at https://snapdocs-closings.readme.io/.

We also want to call out that most integrations will start by connecting with keys in our demo environments listed below:

API	URL
Token API	`https://login.demo-eks.snpd.io/oauth/token`
Snapdocs Connect API	`https://api.cs-demo0.snpd.io/`
Audience	`https://api.*.snpd.io`

To ensure a trouble-free experience when testing the integration in our demo environment, we will require whitelisting of the IP addresses that will be used to visit the above domains.

This guide is not meant to replace the API details in the documentation. It serves as a setup plan for implementing the Snapdocs Embedded POS Integration, which includes steps required to complete the integration and information needed from your company.

Borrower SSO Instructions (OAuth or SAML 2.0)

If your company plans on using the POS login for authentication, please take a look at the following guides.

Please follow the instructions on the following pages

POS Keys

Handling multiple lender Keys for your POS connections is important if you have plans to integrate with multiple lenders. If your integration is for your singular POS, the below best practice suggestions can still apply.

We will provide you a new key and secret for each lender that will be using the POS integration. We will specify if this is a production key, or if it works with the demo environment mentioned above.

We recommend having some sort of lender Keys storage in the POS listener, such that your API calls will authenticate based on the lender of the webhook from Snapdocs.

The SSO and POS Key implementation is expected to be done per lender for the POS integration.

Create Subscriptions

Using an authenticated session you will Create a subscription to the events you want to listen to via webhooks. This will allow you to receive real-time updates on closings so your integration can automatically trigger interactions for the borrower.