Update Page Email Alert Settings

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.zerionsoftware.com/doc/iformbuilder-v81/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "iFormBuilder V81 MCP server": {
    "url": "https://apidocs.zerionsoftware.com/doc/iformbuilder-v81/mcp"
  }
}

Close
PUT /profiles/{profile_id}/pages/{page_id}/email_alerts/settings

Replaces the CC list, the BCC list or the subject element of the page's email alert. Only the fields in the body are written, and each one replaces its stored value as a whole. An empty list clears cc or bcc. null or an empty string clears subject_element.

Duplicate addresses are stored once. subject_element must name an element of the page with a data type of 1 (Text), 7 (Select), 8 (Pick List), 9 (Multi Select), 19 (Text Area) or 25 (Unique ID). It is stored as the element's own name, whatever the letter case sent.

Authorization

Same as GET /profiles/{profile_id}/pages/{page_id}/email_alerts/settings.

Headers

  • Authorization string

    e.g. Bearer {access_token}

Path parameters

  • profile_id string Required

    id of the profile

  • page_id number Required

    id of the page

application/json

Body

  • cc array[string]

    the full CC list

  • bcc array[string]

    the full BCC list

  • subject_element string | null

    name of the element whose value is the subject

Responses

  • 200 application/json

    OK - the settings were saved. The body is the updated settings, in the same shape as GET.

    Hide response attributes Show response attributes object
    • cc array[string] Required

      addresses copied on each alert

    • bcc array[string] Required

      addresses blind-copied on each alert

    • subject_element string | null Required

      name of the element whose value is the subject; null when none is set

  • 400 application/json

    Bad Request - the body is not a JSON object, cc or bcc is not a list of valid email addresses or is longer than 1000 characters once joined with ,, or subject_element does not name an element of the page that can be a subject. Nothing was written.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 401

    Unauthorized - missing or invalid bearer token.

  • 403 application/json

    Forbidden - the user cannot assign the page.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

  • 404 application/json

    Not Found - page_id does not exist, is not a page of profile_id, or is a form shared from another profile.

    Hide response attribute Show response attribute object
    • error_message string Required

      human-readable reason for the failure

PUT /profiles/{profile_id}/pages/{page_id}/email_alerts/settings
curl \
 --request PUT 'https://api.iformbuilder.com/exzact/api/v81/[servername]/profiles/self/pages/{page_id}/email_alerts/settings' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer {access_token}" \
 --data '{
  "cc": [
    "supervisor@iformbuilder.com"
  ],
  "bcc": [
    "audit@iformbuilder.com"
  ],
  "subject_element": null
}'
Request example
{
  "cc": [
    "supervisor@iformbuilder.com"
  ],
  "bcc": [
    "audit@iformbuilder.com"
  ],
  "subject_element": null
}
Response examples (200)
{
  "cc": [
    "supervisor@iformbuilder.com"
  ],
  "bcc": [
    "audit@iformbuilder.com"
  ],
  "subject_element": null
}
Response examples (400)
{
  "error_message": "cc must be a list of email addresses"
}
Response examples (403)
{
  "error_message": "string"
}
Response examples (404)
{
  "error_message": "The requested resource is not found"
}