Launch Methods
This page explains how your frontend opens the editor after your backend has prepared an editor URL.
Before using either launch method, your backend should complete the flow in Complete Embed Flow: create or reuse the Application access token, create or select an email, generate a one-time code for the End User userId, and return an editor URL to your frontend.
Editor URL
Both launch methods use the same editor URL format:
https://abc.editor.aurorasendcloud.com/thirdApp?code=example_code&id=b7e4a9c2d1f60835&lang=en_USURL parameters
| Parameter | Required | Description |
|---|---|---|
code | Yes | Temporary code generated by your backend through POST /access/code. |
id | Yes | Public email slug ID returned by POST /resource/email or selected from an existing email record. |
lang | No | Editor language, such as en_US, zh_CN, zh_TW, th_TH, or ja_JP. |
Generate a new one-time code every time the editor opens.
iframe
Use iframe when users should stay inside your product page while editing.
<iframe
id="asc-editor"
src="https://abc.editor.aurorasendcloud.com/thirdApp?code=example_code&id=b7e4a9c2d1f60835&lang=en_US"
width="100%"
height="700"
frameborder="0"
allow="clipboard-write">
</iframe>iframe layout recommendations
- Give the iframe enough height for the editor workspace.
- Avoid placing 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;
}New window
Use a new window when the editor should open as a standalone editing step.
HTML link
<a
href="https://abc.editor.aurorasendcloud.com/thirdApp?code=example_code&id=b7e4a9c2d1f60835&lang=en_US"
target="_blank"
rel="noopener">
Edit Email
</a>JavaScript
const editorUrl = 'https://abc.editor.aurorasendcloud.com/thirdApp?code=example_code&id=b7e4a9c2d1f60835&lang=en_US';
window.open(editorUrl, '_blank', 'noopener');Use rel="noopener" for links opened with target="_blank".
Return URL
The Return URL controls where users go after leaving the editor in a new-window or link-based flow.
Configure it from:
Application -> Editor APIUse a Return URL that brings users back to the right workflow in your product, such as:
https://app.yourproduct.com/templatesThe Return URL is not used to deliver saved email content.
Choosing a method
| Method | Best for | Notes |
|---|---|---|
| iframe | In-page editing | Best when your product UI has enough room for the editor workspace. |
| New window | Standalone editing | Best when the editor should be a separate full-page step. |
Save behavior
Saved content is delivered through your Push URL callback, not through iframe state, window state, or the Return URL.
Use Push URL Callback to receive and store saved email content.
Updated 9 days ago
