Learn more about how to get started with the Content Services API in the following sections:
This feature is available on Beefree SDK paid plans only.
Beefree SDK is a complete content design and creation platform for you to build upon. Our objective is to help you create a fantastic content creation experience for your customers inside your software applications.
As this may go beyond the interactions that happen within our email, page, and popup builders, we created an API to offer more assistance. We call it the Content Services API: it exposes a set of services that will help you provide a better experience with how emails, pages, and popups are created, updated, and transformed into different formats.
The Content Services API (CSAPI) – helps you achieve the following:
Retrieving the HTML of an email, page or popup created with a Beefree builder, so you can build a custom UX flow for saving messages. With the CSAPI, you can ask the Beefree system for the HTML whenever you need it.
Updating the HTML of an email, page or popup created with a Beefree builder, without user interaction. Why? For example, the HTML of an email template might need to be updated (e.g. to resolve a newly discovered rendering issue in an email client), and you don’t want to ask your users to open the email with the builder and resave it.
Outputting partial HTML that enables you to reuse code, increase consistency across your templates, and easily maintain your code.
Generating a thumbnail from the HTML, because thumbnails are always nice to have, for all sorts of reasons 🙂
Generating a PDF from the HTML, as your users may want to share or print an email or a page, and PDF is great for that.
Merging shared content (saved rows) into emails and pages that use it (e.g. update 30 emails that use the same footer).
Use Brand Style Management to make template-wide design changes to existing templates quickly and easily.
Generate plain text versions of emails from JSON templates, ensuring emails look sharp and easy to read on any device.
Leverage AI to generate SMS, Metadata (Preheader and Subject), or Summary text from JSON templates.
This service allows the host application to build a custom workflow that doesn’t rely on the onSave callback in the editor (list of available callbacks). Check our reference documentation on how to use the API to get the HTML from a JSON file.
The first reason for this API to exist is a common use case: a transactional message was created months ago, it does not need to be edited in the editor, but its HTML code needs to be updated to benefit from fixes or changes that resolve rendering issues.
As you know, HTML for email is a mix of old markup – needed by email clients with a lack of support for standards – and advanced tricks used to take advantage of modern email client capabilities. The result is an environment that changes continuously, driven by the discovery of new techniques and by software updates released by the most popular email clients and browsers.
Having the ability to update the HTML without user interaction in the editor means ensuring that your customers can take advantage of the latest fixes or improvements, even if the messages are transactional notifications created years ago and never edited.
It’s not common, but it may happen that a browser crashes before the user saves a message they are working on. In this scenario, using the autosave or the onChange callbacks are enough to prevent any work loss. However, the host application ends up storing a message JSON without the HTML counterpart.
This presents the problem as the two files are out of sync, making things hard for the host application to get a preview, and, therefore, hard for the user to understand if they are looking at the right version of the message.
Using the API the host application can generate an updated HTML from the latest JSON, solving the issue.
A step further in the use case described above. Some modern applications remove any “Save” button from the UI, autosaving the work every time a change is applied (e.g. Google Docs). Through the onChange callback, your application can reproduce this behavior, and get the HTML from the saved JSON, when needed.
The API provides some useful services that offer additional message formats, reducing the development effort in the host application.
A dedicated endpoint that transforms an HTML into a PDF document and supports the following options:
Landscape and portrait as available values.
Letter, A4, A3, and Full as available values.
While the other values split the message into pages, the Full option returns a single page using 900px as the page width and the proportional height.
PDF is often used in most approval processes, but is also a perfect format for printers. Check our reference documentation on how to use the API to get a PDF from an HTML file.
An endpoint that creates an image from an HTML source supporting the following options:
Width The image width in pixels
Height The image height in pixels
When the height is not provided, the API applies a proportional value based on the given width, keeping the image aspect ratio. When the Height value is provided, but not proportional to the given width: If it’s higher: the proportional value applies If it’s lower: the image is cropped
Check our reference documentation on how to use the API to get images from an HTML file.
What if a footer is shared by 10 messages and needs to be updated in all of them? The Synced Rows feature was created precisely to address the scenario of content that is shared across multiple emails, pages, or popups, and it is used in conjunction with the Content Services API.
The Merge method of the Content Services API allows you to update a row across multiple messages. More specifically, it allows the host application to update an element in an existing JSON document. This means that, for instance, you could create a feature that takes care of updating existing messages in the background, without any further action by your users.
The Index method of the Content Services API is a complementary method, designed to retrieve the assets which contain saved rows, so that you know which assets need update using the Merge method.
There are many use cases, including:
updating headers & footers;
changing the expiration date in a seasonal offer;
making price changes, link changes, etc. in content that otherwise can be re-used “as is”
etc.
The Content Services API (CSAPI) allows you to carry out a number of useful tasks, like converting an email or a page into a thumbnail image or a PDF document, or updating a footer into all the emails that use it (i.e. a saved row).
These tasks consume resources in our Amazon Web Services environment, so we have to account for that. We did extensive research to define pricing that is consistent with other APIs.
Here is a quick summary:
Essentials
15,000
$0.01
Core
50,000
$0.01
Superpowers
250,000
$0.003
Enterprise
Custom
Custom
There will be no changes to the functionality of the CSAPI, except that we’ve added a really useful Merge API that allows you to update saved rows in the documents that use them. You can find complete technical documentation on the new “merge” method here.
Most changes related to CSAPI will be in the background, but there will be some changes in the Beefree SDK Console, and in terms of billing.
API Key Management: when you configure an application in the Beefree SDK Console, you will see two actions – instead of a single Revoke action – in the area of the application settings where your API key is shown:
Regenerate: Revokes the current key and creates a new one
Disable and revoke: Revokes the current key and disables the service, so you will not be charged for it*
*Note: Extra API calls are charged at the end of the billing period. For this reason, the first invoice after cancellation may include CSAPI charges.
Billing statement changes: you will see new line items on your Beefree SDK invoice.
You can by creating a development application, and then creating a new API key for that app, which will be used for development purposes. Reference our Development Applications documentation to learn how to create one.
An additional charge, CSAPI, will be added to your current subscription plan invoice.
The Content Services API is provided as a component for your current subscription and the charges will be applied to the subscription payment method. Currently, there is no option to use an alternative payment method specific to these charges.
API requests rate limits exist independently of any API key’s monthly usage allowance.
As of January, 2020, the API has the following rate limits:
Per minute: 500 requests
Per second: 100 requests
The Brand Style Management endpoint enables you to manage and modify the style of email, pages, and popup templates. While the Content Defaults feature enables you to set default styles for new content elements like headings, paragraphs, and buttons, the Brand Style Management endpoint takes it a step further. It allows you to make template-wide design changes to existing templates quickly and easily, ensuring that all modules adhere to the broader design system or brand guidelines. In this article, we'll explore what this Content Services API (CSAPI) Brand Style Management endpoint is, its benefits, how to get started with it, and how it differs from Content Defaults.
To apply a style globally, take the following steps:
Manage Brand Styles: Begin by defining your brand's styles within the schema. The Brand Style Management endpoint schema mirrors the . This enables you to easily reuse the styles you’ve already defined in your application’s frontend. Use the same schema to specify colors, fonts, and any other design elements you want to apply uniformly.
Prepare the Template: Ensure you have the JSON template ready, which is the foundation for your branding modifications.
API Call: Make an API call to the CSAPI Brand Style Management endpoint, providing the schema with your defined brand styles and the JSON template to be updated.
API Processing: The API will take care of processing your request. It will automatically merge the specified brand styles into the template, applying the desired changes globally.
Receive Modified Template: After the API processes your request, it will return the modified JSON template with the updated styles. This template is now ready to be used in your marketing campaigns with the consistent branding you've defined.
Authentication is essential to secure access to the Brand Style Management endpoint. We use API keys to authenticate requests. The API key you should use to access this endpoint is the CSAPI API key available in your Beefree SDK Developer Console. If you do not have a CSAPI key in your Developer Console, ensure you have a .
Include the API key in the request header as follows:
/template/brand
HTTP Method: POST
Description: Apply brand styles to a template, ensuring a consistent visual identity.
Request Parameters:
styles (JSON): The brand styles to apply to the template.
template (JSON): The JSON template to be updated with the brand styles.
HTML Return the template with or without HTML.
Example Request:
The following examples displays a button array.
Response Format:
200 OK: The request was successful, and the modified template was returned.
400 Bad Request: There was an issue with the request parameters.
401 Unauthorized: The API key is invalid or missing.
500 Internal Server Error: An unexpected server error occurred.
Example Response:
This section discusses the request formats for the different parameters.
The styles parameter in the request should follow this JSON format:
Note: The mobileStyles and hoverStyles properties are not supported by the Brand Style Management API.
The template parameter should contain your template's JSON structure. Ensure that the JSON structure aligns with the template you intend to update.
The following code shows an example of how to configure the style for headers within the table content block:
For example:
The CSAPI Brand Style Management endpoint will take these styles and merge them with your design template, eliminating the need for complex manual editing.
While both Content Defaults and the Brand Style Management endpoint aim to streamline the design process, they serve different purposes:
Set default styles for specific content types.
Useful for quickly creating new templates with consistent styling.
CSAPI endpoint that enables the development of a user interface that empowers end users to make style changes with ease and speed.
Modify the style of existing templates.
Suitable for users who need to make template-wide design changes or maintain brand consistency on existing templates.
The following section displays an example request. Note that the syntax for the CSAPI Brand Style Management endpoint is similar to the .
You can define multiple classes of buttons, images, and rows by passing an array of styles targeting design elements by their class names. To provide multiple styles, use the className property to define as many styles as you like. Before defining the className within the array, ensure you define the className within the template using the .
Each block style can include attributes such as colors, fonts, borders, and more, depending on your brand's requirements. For additional code samples of each content block type and its respective style customization options, reference the .
Both the (frontend) and Brand Style Management endpoint (backend) include the table content block.
The Brand Style Management endpoint schema is designed to be user-friendly and intuitive. You can use the same you used to style your application’s frontend with the Brand Style Management endpoint.
Can be a part of the .
The Content Services API Reference provides a comprehensive guide to utilizing the Content Services API, which leverages the REST architecture and HTTP protocol for making API calls. This reference document outlines the available collections, including /message, /page, /popup, /amp, /template, and /ai, detailing the resources for each collection. For every resource, this document includes its description, parameters, and example responses and requests.
To use the Content Services API you will first need to obtain a your API Key from the Beefree SDK Console.
To obtain an API Key, take the following steps:
Log into the Beefree SDK Console
Locate the application that you wish to work with, and click on Details
Locate the Content Services API section and click Create New API Key
Acknowledge the message that reminds you that if you exceed the number of API calls included in your plan, you may be charged for overages and click Create Key
Your API key will appear under the Content services API section of your application details.
The Content Services API uses API Keys to authenticate requests for resources. You can manage your API Keys within the Beefree SDK Console. All requests must be made over HTTPS and contain the following HTTP Header:
Authorization: Bearer {token}
API requests rate limits exist independently of API key’s monthly usage allowance.
By default, the API has the following rate limits:
Per minute: 500 requests
Per second: 100 requests
X-Rate-Limit: An integer representing the total number of requests available per cycle. Exceeding the limit per cycle results in a 429 error. (e.g. 500)
X-Rate-Limit-Remaining: An integer representing the number of remaining requests before the next cycle begins, and the count resets. (e.g. 100)
X-Rate-Limit-Reset: A Unix timestamp representing the time the next cycle will begin, and the count will reset.
Retry-After: A Unix timestamp representing the time the application may resume submitting requests.
All API access is over HTTPS, and accessed from the following URL:
https://api.getbee.io/v1/{collection}/{resource}
The following table lists the available collection option and corresponding resources for each collection.
/message
html, pdf, images, merge, index, plain-text
/page
html, pdf, images, merge, index
/popup
html
/amp
html
/template
brand
/ai
metadata, sms, summary
/conversion
email-to-page, page-to-email
The following table provides a few examples of URLs you can use to make specific types of requests.
Request HTML for email
https://api.getbee.io/v1/message/html
Landing Page
Request HTML for a landing page
https://api.getbee.io/v1/page/html
Popup
Request HTML for a popup
https://api.getbee.io/v1/popup/html
AMP
Request HTML for AMP
https://api.getbee.io/v1/amp/html
The following section provides detailed information for each of the resources associated with each collection mentioned in the previous section.
URL: https://api.getbee.io/v1/{collection}/html
Endpoint: /message/plain-text
URL: https://api.getbee.io/v1/{collection}/pdf
Note: The response is a JSON string that will contain the URL of the temporary location of the PDF document. The file is available for 24 hours.
URL: https://api.getbee.io/v1/{collection}/image
Prior to using the image endpoint, ensure you reference the following information.
The HTML is rendered in a fixed window size of 1920x1080 to generate a screenshot, with default viewport widths of 320 pixels for mobile and 1024 pixels for desktop, which may cause cropped previews if the content exceeds these dimensions. A clipping size of 1920x1080 is applied, but it can be customized, and the scale factor adjusts to align the viewport and clipping dimensions. For improved results, using auto height with the size parameter is recommended.
html*
String
A Beefree HTML message.
size
String
Use “size” instead of “width” and “height” when you only know the width and want the height automatically calculated. Required if width and height are not defined.
width
Integer
The image width in pixels. Required if size is not defined.
height
Integer
The image height in pixels. Default applies a proportional value based on the given width, keeping the image aspect ratio. When the value is not proportional to the given width, either will occur: If it’s higher, the proportional value applies, or, if it’s lower, the image is cropped. Required if size is not defined.
file_type*
String
Accepts jpg or png.
URL: https://api.getbee.io/v1/{collection}/merge
URL: https://api.getbee.io/v1/{collection}/merge-rows
When utilizing this feature, it's important to consider adding a handle to the metadata. This handle serves a crucial role in functions such as onDeleteRow and onEditRow. In our provided example, we use a handle named guid. However, users have the flexibility to choose their own handle name according to their preferences and requirements. When selecting a handle name, we recommend you choose something descriptive and meaningful for ease of identification and management within your workflow.
URL: https://api.getbee.io/v1/{collection}/synced-rows
URL: https://api.getbee.io/v1/{collection}/merge/index
The resources in the AI collection accept your template JSON and use generative AI to return text within a JSON object to you.
Prior to getting started with the resources in this collection, ensure you have the following:
Superpowers subscription or higher
OpenAI AddOn installed and configured in your Beefree Developer Console
Content Services API key
Note: OpenAI billing costs apply in addition to the Content Services API billing.
v1/ai/metadata
v1/ai/sms
v1/ai/summary
The Conversion Collection provides you with endpoints that enable you to convert templates from one format to another. With the Email to Page endpoint, you can easily convert your email JSON templates into page JSON. The Page to Email endpoint lets you turn your page JSON templates into email-ready JSON, with the option to disable the HTML sanitizer if needed.
The Email to Page endpoint converts a JSON template created for email into a JSON template optimized for web pages. During this conversion, the following adjustments are applied:
Remove AMP Carousel Any AMP carousels included in the email template are removed, as these are not supported in the page format.
Expand Content Area Width The content width is expanded to 900px to fit the web page format, removing the width constraints typically applied to emails.
Target Attributes Target attributes will not be processed. Remove all link target attributes or set them to "Open a new page." Links will not be modified during the conversion.
Remove Subject and Preheader Email-specific metadata, such as the subject line and preheader text, is removed since these elements are not relevant in the page format.
Retain Comments and Secondary Language Comments and secondary language data in the email template are preserved in the conversion process.
The Page to Email endpoint transforms a JSON template designed for a web page into a JSON template optimized for email. During this conversion process, the following adjustments are made:
Remove Video Row Backgrounds Video backgrounds applied to page rows are removed because email formats do not support video backgrounds.
Replace Embedded Videos with Thumbnails Embedded videos are replaced with thumbnail images. This ensures recipients can preview the content visually without the compatibility issues of embedded videos. Note: Hosted videos will not be converted.
Remove Form Blocks Any form blocks present in the page template are removed.
Adjust Design Content Area Width If the page width exceeds the maximum width supported by the email builder (900px), it is resized to fit within email constraints.
Update Link Target Attributes Target attributes will not be processed. Remove all link target attributes. Links will not be modified during the conversion.
Sanitize Code The endpoint sanitizes the code to ensure compatibility with email standards. When the sanitizer is disabled, the payload looks like this:
Handle Multi-Column Layouts The email builder supports up to 12 columns, which is compatible with the page builder's column configurations.
This endpoint accepts a JSON template to create a plain text version of an email.
Parameters required to generate plain text from a template.
Optional. The output language for multi-language templates.
The template's JSON used to create the plain text document.
Array of row definitions inside the template.
Metadata for the template.
A successful response with the plain text document.
The Merge Rows endpoint enables you to integrate custom fonts and resized images into your designs. It saves custom fonts within the template's JSON, ensuring the correct font is displayed. It also handles image resizing, particularly when the image's initial template width is narrower than the saved row's destination template. To use this endpoint, send your template and rows in JSON format. You will receive a response with an updated template. The rows requiring an update are identified by their rowIdentifier values.
The collection ID or name
JSON payload with the template and rows
Label for identifying rows, usually GUID
An array of Beefree rows in JSON format
HTML and styling for paragraphs
A Beefree template in JSON format
List of available webfonts to rectify missing ones
Updated template with merged rows
Transform a JSON template into an HTML response.
The collection ID or name
JSON payload with the template
Flag to return beautified HTML
For multi-language templates, sets the output language using a valid language code
A BeeFree template in JSON format
The main structure of the template page
Defines the style and structure of the container for the page.
The CSS style attributes for the container.
Background color in hexadecimal or other CSS color formats.
"#FFFFFF"Content and styling for the page.
Contains computed styles for different elements on the page.
Color of the link.
"#FF819C"Background color of the message.
"transparent"The width of the message area.
"675px"General styling for text and fonts.
Font color.
"#000000"Font family.
"Arial, Helvetica Neue, Helvetica, sans-serif"List of external web fonts used in the template.
The font-family definition for the web font.
"'Montserrat', 'Trebuchet MS', 'Lucida Grande', 'Lucida Sans Unicode', 'Lucida Sans', Tahoma, sans-serif"Name of the web font.
"Montserrat"The URL to the web font.
"https://fonts.googleapis.com/css2?family=Montserrat:wght@400;700&display=swap"A description of the template.
"BF-ecommerce-template"Contains all the rows in the page layout.
Defines the columns in each row.
Number of grid columns in the row.
6Content modules within the column.
Descriptor for module styles and attributes.
Computed styles specific to this module.
CSS class for the module.
"left fixedwidth"Width of the module.
"287px"Image properties.
Alternative text for the image.
"Image"Height of the image.
"142px"Hyperlink for the image.
"https://beefree.io"Source URL of the image.
"https://ih1.redbubble.net/image.4902607927.7016/flat,750x,075,f-pad,750x1000,f8f8f8.jpg"Width of the image.
"546px"Template name.
"template-base"Template type.
"basic"Template version.
"2.0.0"Title of the template.
"BF-ecommerce-template"The HTML response
This endpoint accepts HTML and settings to generate a PDF document and provides a URL for the PDF.
Parameters required to generate a PDF from HTML.
The file type for the output.
A full HTML document to be transformed into a PDF.
The orientation of the PDF page.
The size of the PDF page.
A successful response with the PDF document URL.
The MIME type of the PDF file.
The filename of the generated PDF.
The orientation of the PDF.
The size of the generated PDF.
The URL where the generated PDF is temporarily hosted.
The HTTP status code of the response.
Transform HTML and image settings into an image.
The collection ID or name
JSON payload with HTML message and image settings
Accepts jpg or png
The image height in pixels
A BeeFree HTML message
Image size if width and height are not defined
The image width in pixels
The image response as a binary data in PNG format
Retrieve a list of synced rows from a template.
The collection name.
Parameters for the synced rows request.
The label used for identifying the rows added to the metadata key, usually GUID.
The JSON structure of the template.
"#ffffff""#7747FF""transparent""600px""#000000""Arial, Helvetica, sans-serif""<p>I'm a new paragraph block.</p>""#101112""'Alegreya', 'Trebuchet MS', Helvetica, sans-serif""16px""0922fb70-f97e-4ae8-bcfe-0be9fd09a0d5"true"'Alegreya', 'Trebuchet MS', Helvetica, sans-serif""Alegreya""https://fonts.googleapis.com/css2?family=Alegreya:wght@100;200;300;400;500;600;700;800;900"A successful response with a list of synced rows.
The unique identifier for the row, typically a GUID.
"0922fb70-f97e-4ae8-bcfe-0be9fd09a0d5"The index of the row inside the template.
0Reference an array of metadata objects from a Beefree template in JSON format.
The collection ID or name
JSON payload containing the Beefree template
A Beefree template in JSON format
An array of metadata objects containing row details
The endpoint accepts a JSON template and returns a JSON object with metadata.
JSON template and options to generate metadata
Optional settings that provide additional instructions to the AI for metadata generation.
The model to be used for the AI, such as GPT-3.5-turbo.
"gpt-3.5-turbo"Defines the tone of voice for the generated metadata, e.g., 'Formal', 'Humorous'.
""Additional instructions to the AI for metadata generation.
"Try to use a pun."Boolean flag to request usage data from the AI.
trueSpecify the output language using a valid language code.
""A JSON object representing the template structure.
The main content structure of the template.
The body of the template, including container and content styles.
Contains style information for the main container of the template.
CSS properties for the container.
"#fff""none""top left""no-repeat""auto"Contains computed styles and the main content styles.
Computed styles for elements within the content.
"#8a3b8f""transparent""650px"General style attributes for the content.
"#000000""Lato, Tahoma, Verdana, Segoe, sans-serif"Template type used for identification.
"mailup-bee-page-properties"List of web fonts used in the template.
"'Lato', Tahoma, Verdana, Segoe, sans-serif""Lato"URL to fetch the font.
"https://fonts.googleapis.com/css?family=Lato"Basic information about the template.
"template-base""basic""2.0.0"Title of the template.
""Brief description of the template.
""Array of row objects that define the layout of the template.
Defines the grid layout within the row.
Number of grid columns used.
12Content modules within the column.
Module descriptor including styles and attributes.
"center""10px""5px"A JSON object with metadata (preheader and subject).
Preheader text for the email.
"Ready to Bee a part of our user research project? Schedule your interview now!"Subject line for the email.
"BEE Pro: Let's Bee-gin! Join our user research project 🐝"Information about the token usage in the AI request.
42448472Detailed information on completion token usage.
0Replace or update content in the template using a specific path and value.
JSON path of the element to replace.
"$..rows[?(@.metadata.uid=='508824c4-8d45-11ee-84be-aafd6b2aca16')]"The new value that will replace the current content.
4Computed style for the module.
Image details and properties.
Paragraph details and properties.
"mailup-bee-newsletter-modules-paragraph"Style attributes for the column.
"transparent"Styling and metadata for the container.
Conditions for showing the content.
Content metadata and styling.
Metadata for the updated content.
"508824c4-8d45-11ee-84be-aafd6b2aca16"""Successful operation
The transformed HTML output.
The resulting updated JSON structure.
The page content and structure.
The body of the page.
Comments associated with the operation.
This endpoint accepts a JSON template and options to generate a custom SMS.
"gpt-3.5-turbo"Specify the tone of voice for the SMS.
"detailed"Extra instructions for the AI.
true"it-IT""#fff""none""top left""no-repeat""auto"Successful response with SMS.
"Ciao! Ti interessa partecipare a un progetto di ricerca utente con noi? Sarà una videochiamata di 30-45 minuti."47587562This endpoint accepts a JSON template and options to generate a concise summary.
"gpt-3.5-turbo"Specify the tone of voice for the summary.
"concise"Extra instructions for the AI.
true"it-IT""#fff""none""top left""no-repeat""auto"Successful response with summary.
"Vuoi partecipare a un progetto di ricerca utente con BEE Pro? Rispondi a Dalila per prenotare un colloquio video."42539464Converts an email JSON template to a page JSON template, ensuring compatibility by converting or removing unsupported blocks.
JSON payload with the email template to be converted
A BeeFree template in JSON format
Page structure of the template
Background color of the container
"#FFFFFF"Link color in the content
"#0068A5"Background color for the message area
"transparent"Width of the message area
"500px"Font color for the text
"#000000"Font family for the text
"Arial, Helvetica, sans-serif"Template description
"Empty template for BEE"Number of grid columns in the row
12Module type
Module descriptor with styling and content attributes
Paragraph HTML content
"<p>I'm a new paragraph block.</p>""#000000""14px""inherit""c8ecedba-4891-46fa-9aec-1f4ef3276914"falseStyle for the column
"transparent""5px"Template name
"template-base"Template type
"basic"Template version
"2.0.0"Title of the template
"Empty Template"Successful conversion to page JSON template
"#FFFFFF""#0068A5""transparent""900px""#000000""Arial, Helvetica, sans-serif""Empty template for BEE"12"mailup-bee-newsletter-modules-paragraph""<p>I'm a new paragraph block.</p>""#000000""14px""inherit""c8ecedba-4891-46fa-9aec-1f4ef3276914"falseConverts a page JSON template to an email JSON template, ensuring compatibility by converting or removing unsupported blocks. By default, the conversion sanitizes HTML modules, which can be disabled by setting a specific parameter.
JSON payload with the page template to be converted
Option to disable HTML sanitizer
trueA BeeFree template in JSON format
Page structure of the template
Background color of the container
"#FFFFFF"Link color in the content
"#0068A5"Background color for the message area
"transparent"Width of the message area
"500px"Font color for the text
"#000000"Font family for the text
"Arial, Helvetica, sans-serif"Template description
"Empty template for BEE"Number of grid columns in the row
12Module type
Module descriptor with styling and content attributes
Raw HTML content
"<div class=\"our-class\"><script>console.log(\"ok\");</script>test 1</div>""f6c6a079-dd90-4589-8855-93dfdf74461d"falseStyle for the column
"transparent""5px"Template name
"template-base"Template type
"basic"Template version
"2.0.0"Title of the template
"Empty Template"Successful conversion to email JSON template
"#FFFFFF""#0068A5""transparent""500px""#000000""Arial, Helvetica, sans-serif""Empty template for BEE"12"mailup-bee-newsletter-modules-html""<div class=\"our-class\"><script>console.log(\"ok\");</script>test 1</div>""f6c6a079-dd90-4589-8855-93dfdf74461d"false