Other Mers Actions Webhooks

MERS Actions webhook events

This document describes webhook events emitted for MERS Actions so your system can react to eNote updates.

Event names

Event names use the format:

[event]_[outcome]

Outcomes

Outcome	Meaning
`complete`	The action completed successfully.
`failed`	The action failed.
`notification_received`	A MERS notification was received, the action on the eNote was executed by one of your partners

Events

Event	Description	Common examples
`deactivation`	An eNote was deactivated in MERS	`deactivation_complete`, `deactivation_failed`, `deactivation_notification_received`
`deactivation_reversal`	The eNote deactivation was reversed	`deactivation_reversal_complete`, `deactivation_reversal_failed`, `deactivation_reversal_notification_received`
`assumption`	An assumption was performed on the eNote	`assumption_complete`, `assumption_failed`, `assumption_notification_received`
`assumption_reversal`	The previous assumption was reversed	`assumption_reversal_complete`, `assumption_reversal_failed`, `assumption_reversal_notification_received`
`modification`	A modification was performed on the eNote	`modification_complete`, `modification_failed`, `modification_notification_received`
`modification_reversal`	The previous modification was reversed	`modification_reversal_complete`, `modification_reversal_failed`, `modification_reversal_notification_received`
`add_document_to_mers`	A supplemental doc was added to the eNote and MERS was notified of it	`add_document_to_mers_complete`, `add_document_to_mers_failed`, `add_document_to_mers_notification_received`
`add_document_to_mers_reversal`	The latest added document was removed	`add_document_to_mers_reversal_complete`, `add_document_to_mers_reversal_failed`, `add_document_to_mers_reversal_notification_received`
`change_partner`	A partner was updated on the eNote	`change_partner_complete`, `change_partner_failed`, `change_partner_notification_received`
`change_data`	Other data change	`change_data_complete`, `change_data_failed`, `change_data_notification_received`

Events and actions

Each event is associated with one or several possible actions

Event	Actions
`deactivation`	`ChargedOff`, `ConvertedToPaper`, `PaidOff`, `PaperReplacement`, `RegistrationReversal`, `TransferredToProprietaryRegistry`
`deactivation_reversal`	`ChargedOffReversal`, `ConvertedToPaperReversal`, `PaidOffReversal`, `PaperReplacementReversal`, `TransferredToProprietaryRegistryReversal`
`assumption`	`Assumption`
`assumption_reversal`	`AssumptionReversal`
`modification`	`Modification`
`modification_reversal`	`ModificationReversal`
`add_document_to_mers`	`AddDocument`
`add_document_to_mers_reversal`	`DocumentReversal`
`change_partner`	`AddDelegateeForTransfers`, `ReleaseDelegateeForTransfers`, `AddMasterServicer`, `ReleaseSubservicer`, `AddSecuredParty`, `ReverseSecuredParty`, `ReleaseSecuredParty`, `AddSecuredPartyDelegatee`, `ReleaseSecuredPartyDelegatee`
`change_data`	`Update`

Note: ConvertedToPaper and ConvertedToPaperReversal are not allowed actions through our API but notifications could still be sent for those if they happen through the UI or if triggered by one of your partners.

Payload

Webhook requests contain a JSON body with the following structure.

Top-level fields

Field	Type	Description
`mers_action_id`	string (UUID)	Unique identifier for this MERS Action in eVault.
`status`	string	Processing status (e.g. `complete`, `mers_responded_failed`, `snapdocs_error`).
`display_status`	string	Customer-friendly status. `complete` or `failed`.
`action`	string \| null	MERS action category (e.g. `ChargedOff`, `PaidOff`, `Assumption`, `AssumptionReversal`).
`documents`	array	List of impacted documents (see below).
`errors`	array (optional)	Present when one or more per-document errors exist.
`event_timestamp`	string	ISO 8601 timestamp of the event.

`documents[]`

Each entry includes:

Field	Type	Description
`min_number`	string	MERS MIN for the document.
`document_id`	string (UUID) \| null	eVault document id (when available).
`emortgage_package_id`	string (UUID) \| null	eMortgage package id (when available).

`errors[]` (optional)

When present, errors are objects with keys such as:

Field	Type	Notes
`condition`	string	Example: `Error`
`min_number`	string	The MIN associated with the error
`code`	string	MERS error code
`name`	string \| null	May be null
`description`	string \| null	May be null

Example payloads

Action completed

Example event: deactivation_complete

{
  "mers_action_id": "0b6f3a1e-4c9d-4f2a-9b7e-2d8c5e1a7f43",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "status": "complete",
  "display_status": "complete",
  "action": "ChargedOff",
  "documents": [
    {
      "min_number": "12345678901234567890",
      "document_id": "f4dc2c2f-be37-4382-b90d-78ea3a75d095",
      "emortgage_package_id": "71f067f2-2cdd-45bd-90b1-0ed2ea1f6c22"
    }
  ]
}

Action failed (with errors)

Example event: deactivation_failed

{
  "mers_action_id": "d485dc53-2155-465f-a78e-3dd6002304c6",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "status": "mers_responded_failed",
  "display_status": "failed",
  "action": "ChargedOff",
  "documents": [
    {
      "min_number": "12345678901234567890",
      "document_id": "f4dc2c2f-be37-4382-b90d-78ea3a75d095",
      "emortgage_package_id": "71f067f2-2cdd-45bd-90b1-0ed2ea1f6c22"
    }
  ],
  "errors": [
    {
      "condition": "Error",
      "min_number": "12345678901234567890",
      "code": "123",
      "name": "Error name from MERS",
      "description": "Error description from MERS"
    }
  ]
}

Notification received

Example event: assumption_reversal_notification_received

{
  "mers_action_id": "6d3f0c13-e54f-42c7-a963-ce1fa9f271d5",
  "event_timestamp": "2026-05-21T12:00:00Z",
  "status": "complete",
  "display_status": "complete",
  "action": "AssumptionReversal",
  "documents": [
    {
      "min_number": "12345678901234567890",
      "document_id": "f4dc2c2f-be37-4382-b90d-78ea3a75d095",
      "emortgage_package_id": "71f067f2-2cdd-45bd-90b1-0ed2ea1f6c22"
    }
  ]
}