Auto Validation Workflow
Asynchronous workflow
This is achieved when uploading "bulk" data in a CSV format Auto Validation (POST). Each row contains the data for a MIN number
Scenario 1: MIN is already in eVault
If the eNote is already in your eVault the autovalidation is automatically triggered after the data upload. Upon completion a webhook event is triggered that contains the status (result of the auto validation) (passed, failed or cleared)
Scenario 2: Auto Validation data is uploaded before the eNote is in the eVault
If the data is uploaded before getting the eNote delivered to the eVault, the data is persisted and the auto validation is triggered automatically after the eNote is saved to the vault. Upon completion a webhook event is triggered that contains the status (result of the auto validation) (passed, failed or cleared)
Getting more detailed AutoValidation status on a MIN
This is achieved through this endpoint: Show auto-validation data for single enote (GET)
1. Data for this MIN has not been uploaded
The result will be 404: Not Found
2. Data for this MIN has been uploaded but the eNote is not in the eVault
auto_validated is false, document_errors is an empty array and emortgage_package_id is null meaning there is no document matching this MIN and the MIN has not been auto validated.
Sample response:
{ "data": { "id": "38762fac-9011-4cc6-8fed-1f4f244318ff", "type": "auto_val_entries", "attributes": { "min_number": "999938007602270063", "auto_validated": false, "emortgage_package_id": null, "document_errors": [], "updated_at": "2025-09-04T21:28:35.095Z" } } }
3. Data for this MIN has been uploaded and the Auto Validation failed
auto_validated is false, document_errors is an array containing the error description and emortgage_package_id is the ID of the eNote in the eVault
Sample response:
{ "data": { "id": "1583d676-d65b-4562-8861-79f44e4439dd", "type": "auto_val_entries", "attributes": { "min_number": "999938142435612304", "auto_validated": false, "emortgage_package_id": "9ea24526-d938-4db1-93e2-9b7fb821d908", "document_errors": [ { "id": "6d4680a4-645d-491a-a5ac-e737461b9131", "data": { "data": "2020-04-01", "enote": "2019-04-01" }, "csv_header": "1st Payment Date", "code": "1070", "description": "is missing or does not match", "exception_type": "Fatal", "manually_resolved": false }, { "id": "c4806de7-0e32-468a-b533-b8e730e1e8ad", "data": { "data": "200 Montgomery Street", "enote": "100 Montgomery Street" }, "csv_header": "Street Address", "code": "1120", "description": "is missing or does not match", "exception_type": "Fatal", "manually_resolved": false } ], "updated_at": "2025-09-04T12:30:29.427Z" } } }
4. Data for this MIN has been uploaded and the Auto Validation passed or cleared
auto_validated is true, document_errors is an empty array and emortgage_package_id is the ID of the eNote in the eVault.
Sample response:
{ "data": { "id": "d72e5f7b-d0d5-43eb-9fe2-b9b512dfa1c0", "type": "auto_val_entries", "attributes": { "min_number": "999938088849853317", "auto_validated": true, "emortgage_package_id": "5846382f-fb22-4353-bcf4-afcef78e9e36", "document_errors": [], "updated_at": "2025-09-04T21:12:24.305Z" } } }
Synchronous workflow
This is achieved by sending the data for a given MIN in a json format Submit auto-validation data (POST)
Scenario 1. MIN is already in the eVault
If the eNote is already in your eVault the autovalidation is automatically triggered and the result of the auto validation is returned synchronously. A webhook event is also triggered that contains the status (result of the auto validation) (passed, failed or cleared)
When the auto validation succeeds, auto_validated is true, document_errors is an empty array and emortgage_package_id is the ID of the eNote in the eVault.
Sample response
{ "data": { "id": "642f512d-5d51-40c9-930e-b97a3fdf646b", "type": "auto_val_entries", "attributes": { "min_number": "999938016081385003", "auto_validated": true, "emortgage_package_id": "47ee4cfd-0e19-406a-96f8-602ff03ac06b", "document_errors": [], "updated_at": "2025-09-04T21:52:45.765Z" } } }
When the auto validation fails, auto_validated is false, document_errors is an array containing the error description and emortgage_package_id is the ID of the eNote in the eVault
Sample response:
{ "data": { "id": "36873a08-bf8f-4d69-bb9e-1254d028f0b1", "type": "auto_val_entries", "attributes": { "min_number": "999938037252081858", "auto_validated": false, "emortgage_package_id": "c0ff4dbe-d9c5-412b-859b-539d455fa9fb", "document_errors": [ { "id": "deb931b1-fc02-4310-b175-54802ff1dea8", "data": { "data": "Davide", "enote": "David" }, "csv_header": "Borrower 1 First Name", "code": "1040", "description": "is missing or does not match", "exception_type": "Fatal", "manually_resolved": false } ], "updated_at": "2025-09-04T22:01:50.754Z" } } }
Scenario 2. Auto Validation data is uploaded before the eNote is in the eVault
If the data is uploaded before getting the eNote delivered to the eVault, the data is persisted. The response has the record (auto validation entry) ID, auto_validated is false, document_errors is an empty array and emorgage_package_id is null indicating that there is no document corresponding to this MIN in the eVault.
Sample response:
{ "data": { "id": "3d04d284-d96e-4c01-b835-6bdbe6139652", "type": "auto_val_entries", "attributes": { "min_number": "999938016081385003", "auto_validated": false, "emortgage_package_id": null, "document_errors": [], "updated_at": "2025-09-04T21:46:20.306Z" } } }
The auto validation is triggered automatically when the eNote is saved to the eVault. Upon completion, a webhook event is triggered that contains the status (result of the auto validation) (passed, failed or cleared)