Embed with iframe

Use iframe embedding when you want the editor to appear inside your product page.

Your backend still handles authentication and email creation. Your frontend only receives a temporary code and email ID, then renders the iframe.

Basic iframe

<iframe
  src="https://plugin.aurorasendcloud.com/thirdApp?code=TEMP_CODE&id=EMAIL_ID&lang=en_US"
  width="100%"
  height="700"
  frameborder="0"
  allow="clipboard-write"
></iframe>

URL parameters

Backend responsibilities

Before rendering the iframe, your backend should:

1. Create or refresh the End User token.
2. Create or select an email ID.
3. Generate a temporary code.
4. Return code and emailId to your frontend.

Do not generate temporary codes in frontend code.

Frontend example

<iframe
  id="asc-editor"
  src="https://plugin.aurorasendcloud.com/thirdApp?code={{ code }}&id={{ emailId }}&lang=en_US"
  width="100%"
  height="100%"
  frameborder="0"
  style="border: 0; min-height: 700px;"
  allow="clipboard-write"
></iframe>

Layout recommendations

• Give the iframe enough height for the editor workspace.
• Avoid putting the editor inside a small scrollable panel.
• Use responsive sizing if the editor appears inside a dashboard layout.
• Test both desktop and smaller screen widths in your product.

Example CSS:

#asc-editor {
  width: 100%;
  min-height: 700px;
  border: 0;
}

Temporary code handling

Temporary codes are single-use and expire quickly.

Generate a new code each time:

• The editor page loads.
• The user starts a new edit session.
• The previous code expired before the iframe loaded.

Save behavior

When the End User saves, ASC Editor Plugin sends the saved content to your configured Push URL.

Your product should not rely on iframe state alone to retrieve final content. Use Push URL Callback as the source of saved HTML and JSON.