Transfer and eDelivery Webhook payloads

Below are more details about the webhooks payload for transfers and edeliveries.

Please note, the webhook events do not have min_number and other document ids at the root JSON level, as the transaction type supports bulk send multi transaction interactions. Your listener should look for the MIN in either location.

Outbound transfers

This is a transfer initiated by your eVault

{
  "event_type": "transfer_submitted",
  "status": "processing_accept_or_reject",
  "display_status": "pending",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "transfer_id": "xxx",
  "documents": [
    {
      "document_id": "f4dc2c2f-be37-4382-b90d-78ea3a75d095",
      "emortgage_package_id": "71f067f2-2cdd-45bd-90b1-0ed2ea1f6c22",
      "min_number": "999938023518486453"
    }
  ]
}

Outbound eDeliveries

This is an eDelivery initiated by your eVault

{
  "event_type": "edelivery_submitted",
  "status": "initiated",
  "display_status": "pending",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "edelivery_id": "xxx",
  "documents": [
    {
      "document_id": "f4dc2c2f-be37-4382-b90d-78ea3a75d095",
      "emortgage_package_id": "71f067f2-2cdd-45bd-90b1-0ed2ea1f6c22",
      "min_number": "999938023518486453"
    }
  ]
}

Inbound transfers

This is a transfer received by your eVault, initiated by a third party

{
  "event_type": "transfer_received",
  "display_status": "pending",
  "status": "pending_documents",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "transfer_id": "xxx"
}

For transfer accepted webhook events, the document information will be available only if the inbound eDelivery has been accepted first.

Inbound eDeliveries

This is an eDelivery received by your eVault, initiated by a third party

{
  "event_type": "edelivery_received",
  "display_status": "pending",
  "status": "can_confirm_or_reject_receipt",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "edelivery_id": "xxx"
}

edelivery_accepted_distribution indicates the document was delivered (saved) to the evault at which point the document and emortgage package ids are available. A document is associated with a MIN number whereas an emortgage package is a "version" of that MIN. A MIN is unique per document in your evault but there could be several emortgage packages for one document (or MIN). If there was a redraw of the note for example, there would be two emortgage packages associated with one document. The current "version" (or emortgage package) of the document is referenced by using primary_package_id in the document attributes. For each MIN supplemental_document_count indicates whether additional documents were delivered with the note. A supplemental document is defined as a file having a document type for the list provided by MERS in Appendix B of the eRegistry Programming interface (or see the MERS document types section)

Note that we provide the document information in an array whereas there will only be one document (eNote) per eDelivery. This is because MERS technically allows eDelivery and Transfer of several documents at once but it is not used because not all eVault providers support this feature.

{
  "event_type": "edelivery_rejected_distribution",
  "display_status": "rejected",
  "status": "disapproved_distribution",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "edelivery_id": "xxx"
}