Retrieving HTML and CSS (Legacy Compatibility)

Returns HTML with developer markup and classes, along with CSS, to be stored within your database. This method ensures that when a customer wants to open an email with the editor (old plugin) next time, the stored HTML and CSS can be sent to the editor, maintaining compatibility with legacy systems and preserving the email's design and structure.

Server

Client Libraries

Shell Curl

Methods

Methods Operations

get/coediting/v1/email/html-css

Get HTML and CSS of email template

Get HTML with developer markup and classes, along with CSS

Headers

ES-PLUGIN-AUTH
Type: string
required

Stripo plugin auth token in the format - Bearer ${AUTH_TOKEN}
ES-PLUGIN-UI-DATA
Type: string
required

JSON string with parameters to identify email (Same as metadata param in UI editor). For example: {"emailId": "id1"}

Responses

200
Type: object
css
Type: string

CSS of email template

emailId
Type: integerFormat: int64

ID of email

html
Type: string

HTML of email template

syncModules
Type: array integer[]

List of IDs of sync modules what was found in the HTML (only in case you've activated the Synchronized Modules)

utm
Type: object

get/coediting/v1/email/html-css

curl /coediting/v1/email/html-css \
  --header 'ES-PLUGIN-AUTH: ' \
  --header 'ES-PLUGIN-UI-DATA: '

Show Schema

{
  "html": "string",
  "css": "string",
  "emailId": 1,
  "syncModules": [
    1
  ],
  "utm": {
    "source": "string",
    "medium": "string",
    "campaign": "string",
    "content": "string",
    "term": "string",
    "custom": {
      "propertyName*": null
    }
  }
}

HTML and CSS of email template

Retrieving HTML and CSS (Legacy Compatibility)

Methods

Get HTML and CSS of email template

Models

{} HtmlCss

{} UtmParams