EAD Enterprise Suite icon

EAD Enterprise Suite

MCP server for EAD Enterprise Suite - signatures, evidence, notifications, dossiers via AI agents.

Actions78

Notification → Add Notification Receiver

AI-generated

Summary

Adds a receiver to a notification request for a case file by sending the receiver details and delivery or authentication options to the EAD Enterprise Suite API.

Inputs

  • Case File ID (required) — Identifies the case file.
  • Notification Request ID (required) — Identifies the notification request to receive the new receiver.
  • ID — Optional UUID v4 receiver identifier; the UI says to leave it empty for automatic generation.
  • First Name (required) — Receiver’s first name.
  • Last Name (required) — Receiver’s last name.
  • Email (required) — Receiver’s email address.
  • Phone Number — Receiver’s phone number. The UI says it is required for ADVANCED signature requests and needed for OTP or WhatsApp delivery.
  • Phone Prefix — International dialing prefix for the phone number. The UI says to provide it whenever a phone is used.
  • OTP Required — Whether to require an OTP to open or sign. Defaults to false; the UI says phone-authenticated signature types such as ADVANCED require this to be true and require a phone number.
  • Send WA URL — Whether to deliver the access URL over WhatsApp. Defaults to false; the UI says this needs the receiver’s phone number and prefix.
  • Send SMS URL — Whether to enable SMS URL delivery. Defaults to false.

Output shape

A single API response item.

The provided source pack shows the execute method and API helper names, but omits their bodies, so the response fields and exact request behavior cannot be established from this source.

Links

Discussion