Changelog

Enote status was added to the response of the /closings/{closing_uuid}/status. Reference https://snapdocs-closings.readme.io/reference/getstatus.

Signature name was added to the response of the /closings/{closing_uuid}/borrowers endpoint.Reference https://snapdocs-closings.readme.io/reference/getborrowers.

We fixed a defect in our authentication token verification process.

Two endpoints are now available to allow borrowers to opt out or in to eSigning. Reference https://snapdocs-closings.readme.io/reference/optinesigning and https://snapdocs-closings.readme.io/reference/optoutofesigning

Some borrowers prefer a signature name, which is different from their legal name. We're now allowing lenders to send that preferred signature name to Snapdocs via the API. Reference https://snapdocs-closings.readme.io/reference/closingscreate for details.

To get the status of a closing, call the /closings/{closing uuid}/status endpoint. To specify which closing, use the closing UUID. Reference https://snapdocs-closings.readme.io/reference/statusindex for details.

You can now access closing audit trails by calling the api/v1/closings/{closing_uuid}/audit_trail endpoint. To specify which closing, use the closing UUID, or query the audit events of a specific date. Reference https://snapdocs-closings.readme.io/reference/closingsaudit and https://snapdocs-closings.readme.io/reference/closingsauditquery for details.

When a user calls the GET /api/v1/closings/{closing_uuid}/borrowers endpoint, the detailed scenarios and their respective statuses will return. Click this post to see the list of detailed scenarios.

On Feb 03, we deployed to production three new endpoints to the Snapdocs Connect API that are available without any configuration and/or enablement. Click this post to see the list of new endpoints.