Push URL Callback

The Push URL callback sends saved email content from ASC Editor Plugin to your backend.

Configure a Push URL before production use. This is how your product receives the final HTML and editor JSON after an End User saves an email.

Configure Push URL

Open:

Application -> Editor API -> Push URL

Enter an HTTPS endpoint from your backend.

Example:

https://api.yourproduct.com/webhooks/asc-editor-save

When the callback is sent

ASC Editor Plugin sends a callback when an End User saves email content in the editor.

The callback is used by both editor launch methods:

iframe
New window

Expected response

Your endpoint should return HTTP 200 after the content is accepted.

Example:

HTTP/1.1 200 OK
Content-Type: text/plain

OK

Return 200 only after your backend has processed or stored the content.

Example payload

The callback payload contains the saved email content and metadata.

Example decrypted payload:

{
  "emailId": "email_7b2a1f9c",
  "userId": "user_12345",
  "name": "Welcome Email",
  "subject": "Welcome to our platform",
  "html": "<!DOCTYPE html><html>...</html>",
  "json": {
    "body": {
      "rows": []
    }
  },
  "timestamp": 1780322400
}

Field names and encryption behavior may depend on the final API configuration for your Application. Use the API Reference and test callback to verify the exact payload before launch.

Processing recommendations

Your Push URL endpoint should:

Verify the request format.
Store the latest HTML and editor JSON.
Handle repeated saves from the same End User.
Return HTTP 200 after successful processing.
Log failures for debugging.

Idempotency

End Users may save the same email multiple times.

Design your endpoint to safely process repeated callbacks. Use fields such as emailId, userId, and timestamp to decide whether an incoming callback is new, duplicate, or older than content you already stored.

Encryption

If encrypted callbacks are enabled for your Application, ASC Editor Plugin sends encrypted content that your backend must decrypt before processing.

Keep your private keys secure and do not expose them in frontend code.

Use Code Examples for implementation patterns, and verify the final encryption format in the API Reference before launch.

Testing

Before production use:

Configure the Push URL.
Open the editor with a test End User.
Save an email.
Confirm your endpoint receives the callback.
Confirm your backend stores the returned HTML and JSON.
Confirm your endpoint returns HTTP 200.