Overview

When you load a Beefree application inside the host application, you pass a configuration object with multiple sections that define the characteristics of the UI, UX, and available elements. However, there are cases when you may want to reload this configuration without the need to reload the Beefree application. In these cases, you can use a specific event to update the configuration while the editor is open.

Use cases

With this event, you can make on-the-fly changes to the user experience. For example:

• Updating available categories for Saved rows

• Refreshing a for authorization

• Changing for the current user

• Updating settings for the editor’s

You can load the configuration changes via a new instance event. Here’s an example:

Overview

The debug parameter in the beeConfig is an optional object that enables internal debugging features within the Beefree SDK editor. It's designed to help developers inspect configurations, translations, and data structures more easily during development.

How to Use

You can pass the debug parameter directly in your beeConfig object when initializing the editor. Alternatively, you can set or update it live using the loadConfig method—no need to refresh the editor.

Example (in beeConfig):

Set it live (no refresh needed):

The debug parameter in the Beefree SDK configuration accepts the following parameters:

• all (boolean): Enables all available debug options (inspectJson and showTranslationKeys). Use this during heavy debugging sessions.

• inspectJson (boolean): Adds an eye icon in the toolbar that allows you to inspect the specific JSON used for that element. Useful for understanding how your configuration is being rendered.

The debug parameter is particularly helpful in the following scenarios:

• You're troubleshooting UI rendering issues tied to configuration JSON.

• You need to inspect what exact data is being used for rows/modules.

• You're working on translations and want to ensure correct keys are being used.

Manage users in the Console

You can invite additional users to your Beefree SDK Console. To do so, select Manage users from the personal menu in the top right corner of the screen.

The user that initially created the account is identified as the Account Owner and can add users from this page.

Additional users will be identified as Admins.

The Account Owner has the following additional privileges, compared to Admins:

• Add, edit or delete users, as described above.

• Turn on , using tokens provided by mobile apps like Google Authenticator or Authy. 2FA can be enabled either for specific users, or account-wide from the Settings & Security section in the personal area ().

• Change the company’s name, also in Settings & Security.

Fetch a list of all Tags

/v1/catalog/tags

HTTP Method: GET

Description: Retrieve a full list of all the Tags in the catalog. Tags are keywords tied to templates, helping you find and sort templates based on certain themes or attributes.

Request Parameters

The following table displays request parameters.

Here is a list of terms used frequently throughout the Beefree SDK technical documentation. Things can get a bit tricky when embedding a software application within another software application, so this page is an attempt to create as much clarity as possible. We hope we find it useful. If anything sounds confusing or if you have any suggestions for improvement, please .

• Beefree SDK A toolkit that includes white-label, no-code builders for emails, landing pages, and popups. The toolkit also provides a range of components, APIs, sample code, and support services to help you seamlessly integrate into your software a content creation workflow that your customers will love.

• Beefree SDK subscription

A Release Candidate (RC) Environment is a crucial part of the deployment workflow designed to provide Enterprise customers with additional stability and assurance before a feature reaches full production. Unlike standard releases, which immediately roll out updates to all users, the RC environment acts as an intermediate step. It allows selected customers to access a production-ready version of the latest code before it becomes available to the wider user base. This controlled rollout process mitigates risks associated with unforeseen bugs and ensures a smoother transition. It also mitigates the risk of regressions and rollbacks. By implementing an RC environment, Beefree SDK enables Enterprise customers to conduct their own QA testing on new features, reducing potential disruptions when updates go live.

The following list includes some of the most commonly referenced benefits of utilizing the Release Candidate Environment.

• Risk Mitigation: Enterprise customers can validate new updates in a stable, production-like setting before they are fully deployed.

Beefree SDK's Content Services API uses bearer tokens to authenticate requests. You can create, view, and manage your bearer token in the . All requests must be made over HTTPS and contain the following HTTP Header:

To use the Content Services API you will first need to obtain a your API Key—the bearer token you will use to authenticate to make API calls—from the Beefree SDK Developer Console.

To obtain an API Key, take the following steps:

1. Log in to the .

Beefree SDK's Content Services API uses bearer tokens to authenticate requests. You can create, view, and manage your bearer token in the . All requests must be made over HTTPS and contain the following HTTP Header:

To use the Template Catalog API you will first need to obtain a your API Key—the bearer token you will use to authenticate to make API calls—from the Beefree SDK Developer Console.

To obtain an API Key, take the following steps:

1. Log in to the .

/v1/catalog/categories

HTTP Method: GET

Description: Retrieve a list of all the Templates within the catalog, applying filters based on request parameters.

You can extract a list of all the Categories present within the catalog. This comprehensive list includes all categories under which templates are classified.

The response that you receive is paginated for ease of reading and navigation. It displays 200 items per page by default, providing a comprehensive view of the catalog content.

/v1/catalog/collections

HTTP Method: GET

Description: You can pull up a full list of all Collections in the catalog. Collections are groups of templates with similar attributes or purposes. This overview can help you understand the types of template groupings available.

The response will be paginated, with 200 items per page default for easy navigation. However, you can change this default by adjusting the ‘pagesize’ request parameter to suit your viewing preferences.

The following table displays request parameters.

/v1/catalog/designers

HTTP Method: GET

Description: Access a complete list of all Designers in the catalog.

The response is paginated, with a standard display of 200 items per page. You can manipulate the ‘pagesize’ request parameter to control the number of items shown per page.

The following table displays request parameters.

Beefree SDK's HTML Importer API uses bearer tokens to authenticate requests. You can create, view, and manage your bearer token in the . All requests must be made over HTTPS and contain the following HTTP Header:

To use the HTML Importer API, you will need an API Key, which is the bearer token you will use to authenticate, from the .

Take the following steps to obtain your API key:

1. Log in to the .

Self-Hosted Saved Rows allow you to control where and how your rows are stored and managed, offering flexibility to meet your application's unique requirements. This option is ideal for teams with development resources who want to integrate row storage into their existing infrastructure.

When users save rows, the data includes layout, content, and style settings. This data needs to be stored and managed, typically in your own database, to make rows available for reuse within your design builder.

1. Storage Use a database or storage solution to house self-hosted saved rows. Examples of a few options include:

MIME types are a standardized way to indicate the nature and format of a file, specifying what kind of data it contains. Groups are categories that aggregate these MIME types for simplified handling and management in applications like File manager. This organization allows for custom limitations and processing based on file type.

The following list shows which specific mime types are mapped to our group names for custom limitations on File manager.

By default, newly created applications of both free and paid plans only allow the upload of image, video and PDF file types. If you are on a paid plan and want to allow more file types, you have to enable them in the SDK Console. .

Please also note that the system altogether prevents the upload of potentially harmful file extensions such as exe, msi, bat, iso, jar, apk, SVGs containing JavaScript, HTML with redirects and more.

When working with files, mime types and groups, ensure you consider the following:

Besides the client-side configuration parameters that you can set for your instance of Beefree SDK, you also can specify some server-side configuration options.

To access server-side configurations, log into your and select the application that you wish to configure.

In the application’s details page, locate the area called Application configuration.

Manage roles is used to manage user roles. For details on this feature, see “user roles and permissions“.

Click on Open configuration to manage the server-side settings like:

Enterprise customers can request to inject external JavaScript libraries, like FullStory or Heap, into Beefree SDK when the integration is initialized as part of the .

Custom JavaScript requires a complete technical evaluation by the Beefree SDK development team. The assessment will undergo security, technical and compatibility assessments.

Contact our Sales team and ask to run a script to get started with custom JS libraries injection. Once you contact us, we will take the following steps to complete your request:

1. Our representative will forward your request to our development team

If you are thinking of moving from a different content creation platform to the Beefree SDK, know that you are in good hands. Thousands of applications have been using our embeddable content builders since 2014, which means that our team has encountered a large variety of scenarios and guided customers like you through all sorts of migrations. We're here to help.

We're known for providing a high level of support, which includes everything from the detailed technical docs that you are reading on this site, , and all the way to dedicated Slack channels for . We will learn about your business with an initial consultation followed by meetings with solution engineers, and set you up with an extended proof-of-concept period that allows you to get everything ready for your migration.

If your users have created a library of designs in your legacy tool, we know one of the key questions is always: "How do I get existing designs into Beefree without having to ask my users to recreate them from scratch?"

We've got you covered here:

Your customers' existing designs will not need to be recreated from scratch in the Beefree builder. You can leverage the to take standard HTML emails and turn them into our proprietary JSON format.

Integrating and Testing the Page Builder

When you create an application in the Beefree SDK Console, you’ll be asked to select either Page or Email Builder. Paid applications allow you to create child development applications, to ease new feature testing, development, and maintenance.

Page and Email builders share the same core functionalities, including authentication and configuration. If you already integrated our Email builder, you can re-use most of your work by using the same configuration and callbacks. If this is your first approach to our builders, just follow the Installation section in our documentation. All the documentation in this site applies to both products, except where noted.

All builders are available to Beefree SDK customers under the same all-in-one pricing. Please contact your Customer Success Manager for more details.

The experience

We aim to provide the foundations needed to build a delightful page building experience. We started with the basic features that are already provided to design awesome email messages and tweaked them to work for Web pages.

Once launched as Page Builder, an application will have a few but noticeable differences from the Email builder experience:

• width for pages can be expanded up to 1440px;

• the stage can be scrolled horizontally;

• the sidebar can be collapsed to provide more workspace – useful when working with larger widths;

If you’re on a paid plan, you will also get support for forms and embedded videos.

• You can define and pass forms to the builder, and use the form content block to retrieve and style those forms.

• You can use the video content block to embed and playback videos hosted on Youtube and Vimeo, or point to a hosted video in MP4 format.

This section includes additional resources for integrating and implementing the Page Builder. It also includes resources for integrating the within the Page Builder.

• : An introduction to creating valid Form structures within Beefree SDK.

• : A repository of example Forms you can reference and use to get started.

• : A repository of example implementations of Forms within Beefree SDK. These three example implementations include: creating a default form, creating a form library, and creating a Form builder all within Beefree SDK.

Our Github account hosts useful resources, including sample code to quick start your integrations.

Creating an application

When you log into the Beefree SDK Console you can immediately see what type of applications you have already created under your Beefree SDK subscriptions. To create a Popup application, head over to the Popup Builder Application section and click on Activate.

Once created, head over to “Details” for all server-side configurations. Paid applications allow you to create child development applications, to ease new feature testing, development, and maintenance.

All builders share the same core functionalities, including authentication and configuration. If you have already integrated our Email builder, you can re-use most of your work using the same configuration and callbacks.

Integrating the Popup Builder

Out-of-the-box, the setup and configuration are the same as Email and Page Builder. This section will cover the settings specific to Popup Builder. Check out our Getting Started guide if you’re new to Beefree SDK or unfamiliar with the configuration basics (as seen in the example below).

beeConfig: {
  container: 'bee-plugin-container', // [mandatory]
  ...
}

Loading Popup Builder with no additional settings will give the end-user a beautifully designed popup and workspace to design their content. However, Popup Builder comes with an additional, robust set of configuration options to customize the workspace. This allows the host application to build a workspace that matches their popup’s look and feel and that of the destination page.

For example, the host app can customize…

• The popup workspace background to view how the popup will look “in context” on the destination page.

• The theme and position of the popup for both desktop and mobile design modes.

Continue reading to learn more on how to customize the workspace, starting with the common settings and working up to a full custom layout.

In Email and Page Builder, the Beefree SDK HTML parser service converts your template into an HTML document customized for email or pages, respectively. However, the Popup Builder will not return a full HTML page because the host application is the final destination. In addition, Beefree SDK Popup Builder doesn’t provide the scripts to control the popup’s behavior, such as opening and closing. Rather, Popup Builder provides the HTML “partials” to embed within your popup’s content area or body.

The HTML partial will come with all the CSS required to look as it did in the preview mode. The parser service will wrap the content with a special container to clear all the host application styles and prevent style conflicts. The HTML output is designed to be embedded into any popup framework or application and still render the way it appears in the builder.

Our Github account has some resources that might help you out when testing and integrating the Popup Builder.

Examples of different implementations and configurations that you can draw from to speed up your development.

A collection of ready-made templates that you can use right away and add to your application.

Overview

Saving your end users time when creating designs is more important than ever—especially as AI continues to reshape expectations. Today’s users want to move fast, and increasingly expect to generate polished, on-brand designs with just a prompt or a click. Simple Schema is built to meet that demand. It provides you with the building blocks you need to construct an AI-assisted content creation experience for your end users. This provides them with a faster, more flexible way to build emails, landing pages, and popups instantly inside your application.

Simple Schema empowers your team to unlock AI-assisted content creation and headless template generation—making it easier than ever to build designs programmatically, and 100% outside of Beefree SDK's visual builders. Whether you're building emails, landing pages, or popups, you can leverage Simple Schema as a lightweight, intuitive format that AI models can easily understand and generate.

Headless Template Creation with AI

Simple Schema is designed for flexibility, making it ideal for AI-assisted and headless workflows. Imagine a tool where users describe the design they want in plain language, and submit that description to an AI agent. On the backend:

• An AI model receives the description and generates a Simple Schema-compatible template.

• This template is passed to the /v1/conversion/simple-to-full-json .

• The API returns the complete Beefree JSON for the entire template.

• The template is loaded in the builder, and the end user can start applying edits in a no-code environment.

The following GIF displays an example UI with a basic AI Email Design Assistant that connects to Simple Schema on the backend. By building your own UI and AI agent, you can leverage Simple Schema on the backend to programmatically build templates and load them in the Beefree SDK builder for your end users to use. The programmatically-created email template is loaded within the Beefree SDK builder, and ready for editing.

Navigate to the to run the code for this demo locally on your machine and experiment with .

Using for AI-driven design creation offers the following benefits:

• AI-ready: A simplified format perfect for machine-generated layouts.

• Headless by default: Build and deploy templates entirely outside the visual builder.

• Production-ready: Easily convert to Beefree JSON with a single API call.

This endpoint is essential for converting AI-generated or manually assembled Simple Schema templates into full, builder-compatible Beefree JSON. Learn more about how to use this endpoint in the .

Overview

The resources in the AI collection accept your template JSON and use generative AI to return text within a JSON object to you.

Available Collection Value for AI Endpoints

The following table lists the collection values available in this category of endpoints, and their corresponding collection options.

Prior to referencing the table, the following example shows how you can replace the {collection} placeholder with ai.

How to Replace the {collection} Placeholder

The following example URL has a {collection} placeholder. This placeholder needs to be filled in with a Collection Option prior to making an API call.

https://api.getbee.io/v1/{collection}/sms

As an example, if you'd like to generate SMS text using this endpoint, replace {collection} with ai.

The final URL to make the API call will be:

https://api.getbee.io/v1/ai/sms

The following table provides a comprehensive reference of all available options based on what you'd like to generate.

Prior to getting started with the resources in this collection, ensure you have the following:

• Superpowers subscription or higher.

• An configured within the .

• Content Services API key.

v1/ai/metadata

v1/ai/sms

v1/ai/summary

Get a list of all Templates

/v1/catalog/templates

HTTP Method: GET

Description: Retrieve a list of all the Templates within the catalog, applying filters based on request parameters.

You can execute a search by providing a series of terms within the ‘search’ request parameter. This search will operate on template title, description, category name, collection name, designer name, publication date (‘published_at’), and tags.

The response will encompass a ‘facets’ field, outlining the count of existing Templates across each Category, Collections, Designers, and Tags fields and their sub-fields, considering any applied filters and searches.

The response is paginated, presenting 20 items per page by default. The ‘pagesize’ request parameter enables control over the page size.

The following table displays a list of request parameters.

/v1/catalog/templates/:slug

HTTP Method: GET

Description: Fetch a single template identified by its slug (in the URL).

Overview of Form Block

The Form Block allows you to integrate no-code form creation within your implementation of Beefree SDK. This is helpful in scenarios where your application's end users may want to add forms to their page or popup designs.

Forms are an important part of the content creation workflow, because they enable your end users to gather important information and data relevant to their campaigns and workflows. This data can then be used for future targeted campaigns, personalized content, and so on.

There are several ways you can integrate the Form Block within Beefree SDK to provide your end users with a customized experience that is tailored to their use cases and needs. A few of these customizations and use cases are the following:

• Configure a default form within the Form Block that your end users can then drag-and-drop onto the stage and edit.
• using the Form Block that your end users can use to browse Form templates, select their favorite one, and edit it within the builder.
• that your end users can use to build their own custom form, load them into their page or popup design, and edit as needed.

You can find sample projects for each of these scenarios in the . You can also find the and in this .

Reference the following resources to learn more about how to use the Form Block within Beefree SDK:

• Video

Synced Rows

Synced Rows expands on the foundational capabilities of Save Rows and Edit Single Row Mode, helping users manage rows more effectively. Using the merge-rows and synced-rows methods in the Content Services API (CSAPI), you can create an efficient row management workflow. This ensures that when users update content in one row marked as “synced,” those updates are reflected across all connected designs using that synced row.

Prerequisites

• Self-hosted Saved Rows

Key features

• Cross-design synchronization: Sync saved row contents across multiple linked designs.

• Design consistency: Lock rows in linked designs to keep designs uniform.

• Editing flexibility: Convert rows from synced to unsynced, making individual changes as needed.

• Intuitive edit indicator: Look for the pencil icon at the top-right of synced rows, which provides access to editing options

• Auto-updating contacts: Change a contact in one email, and it updates across multiple campaigns.

• Effortless re-branding: Edit your logo once and watch it reflect across all designs.

• Unified transactional footers: Update details like copyright or social links, and it automatically updates in all relevant email templates.

• Row details: This includes structure, settings, and styles.

• Content details: Settings and styles of individual content blocks.

• Metadata: Any metadata tied to the saved row.

With you can offer an easier way for your end users to modify a single row with a tailored UI built to edit the row structure, content, and style settings without interfering in the overall design of the email campaign, landing page, or pop-up.

complements both and , because it allows complete control over the content of an individual row (for example, a footer that requires an update) without the need to intervene in a full template's design. This will help you in implementing a more effective way to manage libraries of and with a streamlined design and editing process.

Overview

The Image Title Attribute allows end users to add a custom title attribute to images in their email, page, or popup designs.

Adding a title attribute is an important step toward improving accessibility and user experience. When present, the title attribute provides additional context when a user hovers over an image. Also, screen readers can use it to deliver a verbal description, helping visually impaired users better understand the image in context.

By enabling the title attribute option in the Beefree SDK Developer Console, your end users can add a custom title attribute to images in their designs, which serves a different purpose than alt text.

When activated, the Image Properties in the editor will show a new Title attribute field. The following image shows an example of what this looks like in the builder.

How to Activate the Feature

The Image Title Attribute is off by default and can be enabled through the Beefree SDK Developer Console.

Take the following steps:

1. Log in to the .

2. Navigate to the application where you want to enable the feature.

3. Click on the Details button.

4. Navigate to

Once activated, the Image module in the editor will display the Title attribute field, allowing end users to customize it directly.

When an end user adds a custom title attribute, it will appear in the template JSON alongside the existing image properties.

Example:

Consider the following when enabling the the Title attribute for Images in Beefree SDK:

• Alt vs. Title: These are separate attributes. End users can define unique values for each, ensuring improved accessibility and SEO compliance.

• Fallback behavior: If no Title is defined, the field will remain empty, and only the Alt text will be available.

• Accessibility best practice: The Title attribute should complement, not duplicate, the Alt text. Alt text provides an essential image description, while Title add supplemental context.

Building web pages with Beefree SDK

Beefree SDK Page Builder will help your customers create beautiful, responsive landing pages, complete with forms and embedded videos. Combined with our Email Builder, you’ll have the power to deliver to your customers a single, optimized user experience for designing both emails and web pages.

This page provides a high level overview and explanation of what the Page Builder is. Navigate to the following resources to learn more about how to get up and running with the Page Builder:

• Integrating Page Builder

You can use the to convert existing email designs into landing pages. This is useful in scenarios where you may want to reuse content across different channels.

With the Page Builder, your customers can create landing pages and one page sites. In addition, you will find exclusive features that make sense for web pages, such as forms, embedded videos, and the ability to paste scripts, like an embeddable SurveyMonkey or Typeform survey.

Here are a few examples of web pages your customers can build with:

• Product showcase or teaser

• Disclaimer (e.g. age verification)

• Registration (e.g. events, gated content)

You can also create stunning one-page websites where all content is neatly organized on a single, scrollable page. With this approach, page viewers can easily navigate one centralized page using menus and anchors, replacing traditional multi-page layouts.

Pricing for Beefree SDK is based on the concept of unique users of the editor. A unique user is one that is identified by a unique UID, as described below. The system counts unique UIDs within a billing period, and resets the count to zero at the start of the next billing period.

Properties

The UID parameter:

• Is an alphanumeric string passed to Beefree SDK throughout the server-side authorization process.

• Can contain letters from a to z (uppercase or lowercase), numbers and the special characters “_” (underscore) and “-” (dash).

• Make sure that you pass a string, not a numeric value. So even if your UID is a number, pass "12345" and not 12345.

• The UID should not be Personal Data, as indicated in the Beefree SDK License Agreement. Further information about how your use of a Beefree SDK service relates to the EU’s General Data Protection Regulation (GDPR) may be found . Our Privacy Policy, which describes the processing activities carried out by Beefree SDK as Data Controller, is available .

It uniquely identifies a user of the application. When we say “uniquely”, we mean that:

1. It will be counted as a unique user for .

2. Images (and other files) used by the user when creating and editing messages will be associated with it and not visible to other users (when using the default storage).

It’s entirely up to you, as the host application, to determine when to use a new UID at the time you initialize the editor for your users. In 99% of the cases: one UID = one CLIENT ACCOUNT in your application. Sub-users of a client account typically share the same UID.

A quick example to help you visualize this.

• We use the UID in the File Manager to identify where images will be stored

• You typically don’t want client ABC to see client XYZ’s images

• So you will use a certain UID for client ABC and another UID for client XYZ

UIDs in production are counted separately from UIDs in a . For example, if you have the following UID in both a production and development application, the unique UID will be counted twice toward your plan's allotment.

In this scenario, Beefree SDK will treat these as two distinct users, and count this UID twice—once for each environment. Reference for more information on Beefree SDK plan types and their corresponding uid allotments.

Overview

In this article, we will discuss how to sign up for an account in the Beefree SDK Developer Console, create an application, and obtain your Client ID and Client Secret.

This article will cover steps for the following processes:

• Sign up for an account in the Developer Console

• How to create an application

The first step to experimenting with and embedding Beefree SDK's visual builders is to.

Take the following steps to sign up for a Beefree SDK account:

1. Navigate to the .

   1. Complete the required fields to create an account.

   2. Once the form is complete, click Sign up to embed Beefree SDK.

1. Check your inbox and verify your email address.

   1. Once it is successfully verified, you'll be redirected to the . Enter your email and password to login.

2. You'll be redirected to a page with an active free subscription called MyFirstSubscription. Under this subscription, there are four applications you can activate: Email Builder, Page Builder, Popup Builder, and File manager. You can activate one or all of them if you'd like.

Once that’s done, you will be able to . Your dashboard will look like the following image.

You will have the option to activate any or all of the following applications:

Take the following steps to create an application:

1. Click the Activate button that corresponds with the application you'd like to create.

2. Type in a name for your new application.

3. Click Create.

Your application will look like the following in the dashboard once it is activated:

You have successfully created an application. Now, you can enter the application Details and obtain your Client ID and Client Secret.

Click on your application's Details button to view your Client ID and Client Secret. Use these to authenticate when you initialize it.

With your Client ID and Client Secret, you can use our to experiment with a simple integration of Beefree SDK. You can also get started with .

Reference the following related topics to learn more about customizing your applications, creating development instances, and referencing sample code.

Inside the Beefree Developer Console, you have the option to regenerate the Client Secret for your application. To regenerate your application's Client Secret, take the following steps:

1. Log in to the .

2. Navigate to the application you'd like to update the Client Secret for.

3. Click on the application's Details button.

1. Navigate to Application keys within the application's details.

2. Click Regenerate to generate a new Client Secret.

1. You will be prompted to a modal and asked to confirm your application's name.

2. Complete the App Name field and click Regenerate to complete the action.

Your new Client Secret is now available and ready to use. Your old Client Secret will expire 24 hours after creating the new one. Ensure you replace it in all the necessary environments prior to its expiration.

• Create

What is Beefree SDK?

Beefree SDK is an embeddable no-code builder that gives your end users the freedom to design stunning emails, landing pages, and popups—without writing a single line of code. It’s easy to configure, intuitive to personalize, and built to scale with your needs—whether you're a startup or an enterprise. Built with both developers and end users in mind, it’s designed to integrate easily into your application, scale as your product grows, and provide a flexible, white-label design experience.

For developers, Beefree SDK is easy to work with. You can personalize the design experience by adding simple configuration parameters. Want to enable or disable a feature? Just check a box in the Developer Console, hit save, and the changes are immediately reflected on the frontend. No complicated setup required.

For your end users, Beefree SDK is an intuitive drag-and-drop editor with everything end users need to bring their creative ideas to life—whether they’re creating an email campaign, a landing page, or an attention-grabbing popup. Content blocks like titles, images, lists, tables, buttons, and more are all available right out of the box.

Beefree SDK includes the following features and more:

• Email builder: A creation environment that helps end users quickly create beautiful emails. This environment supports your end users in following email creation best practices recommended by industry experts.

• Page builder: A creation environment that empowers end users to build visually stunning landing pages. They can use a landing page as a link for a call-to-action (CTA) inside emails, to embed forms and capture information, or to create standalone pages.

• Popup builder: The that provides end users with the tools they need to build compelling popups that capture attention.

This site discusses the technical capabilities of Beefree SDK, and how to embed it into your web application. To learn more about the end user experience, and how your end users will interact with Beefree SDK on the frontend of your application, reference the . Markdown files for this guide are available in this , which you can clone and use as a starting point for building a knowledge base for your end users.

If you'd like to test the drag-and-drop user experience and explore how easy it is to customize the editor but aren't quite ready to spin up your own test application, our is the best place for you to get started. This simple, public implementation of the Beefree SDK helps you to:

• Experience how easy it is for your end users to create designs using the intuitive, drag-and-drop editor UI

• Easily test UI customizations (like , rearranging or , or applying )

• Explore how you can to make it editable, and

Check out the following public demo apps built with v0, Lovable, and Replit:

• is a demo application built with that simulates how Beefree SDK's no-code drag-and-drop email builder and editor can be integrated into your web application. The demo application includes static dashboards for campaign performance (open rate, click rate, conversion rate, and revenue), campaign breakdown, and subscriber information. Click the following link to access Email Builder by Beefree SDK:

• is a demo application built with to simulate how Beefree SDK integrates within a Martech application's ecosystem. Click the following link to access Marketing Buddy:

• is a demo application built with

Take the following steps to get started with Beefree SDK in a few minutes:

1. Create an account to access the and obtain your credentials.

2. to get started. Beefree SDK offers a generous Free plan that includes each builder type mentioned in the previous section.

3. Create an application and .

Note: Visit the for a comprehensive list of features and the plan type they correspond to.

Reference Quickstart Guides specific to your tech stack:

Learn more about our three embeddable builders.

In addition to our drag-and-drop editors, we also offer a standalone application, which can be used alongside any of the builders. The File Manager is designed to simplify the organization and management of digital assets. It is an image and document management user interface that can be launched as a standalone application. This allows your customers to quickly upload or manage assets, without having to load one of the builders.

Learn more about our and .

We have a whole library of handy sample code to help you get started with basic Beefree SDK implementations and also learn how to put more advanced features to work. You can check out the available sample code or head straight to .

Learn more about Beefree SDK through . Explore , , and .

The Beefree SDK technical documentation is available at docs.beefree.io/beefree-sdk and in the .

You can contribute feedback to the documentation in one of the following ways:

• On docs.beefree.io/beefree-sdk use the Was this helpful? emoji option on the right hand side of each page. After selecting an emoji, you'll have the option to submit written feedback on what you'd like to see in the documentation. This feedback goes directly to the documentation team and is integrated frequently.

• Creating a pull request using the . Use this option in the event you find a typo, broken link, or small fix.

The Page Builder includes an expanded Video content block for optimized usage of videos on web pages. Videos are added inside an iframe via the HTML5 video tag.

There are multiple ways to add a video to a page built with Beefree SDK. Additional settings allow the video progress bar and loop playback to be turned on or off.

Embedded

The Embedded mode allows video playback inside the page. It requires the URL of a video hosted on YouTube, YouTube Shorts, or Vimeo.

Hosted video

Same as the embedded option, but the URL provided must point to a self-hosted video in MP4 format. Settings for hiding controls and loop playback apply as well. Please note that the player interface your visitors will experience might slightly vary based on the browser they use.

Thumbnail

As a fallback, you may also use the video block for generating a thumbnail, the same way the block works when building emails. Just enter the URL for a video hosted on YouTube, YouTube Shorts, or Vimeo. A thumbnail linked to the video will be created. You may also style the overlay play icon.

• YouTube (16:9 aspect ratio)

  • Public Videos

  • Unlisted Videos

Overview

Setting up two-factor authentication will keep your developer account extra secure. Two-factor authentication means that users will need to provide two different identifications to log in to their Beefree SDK Console: their regular login credentials, and a token generated by a two-factor authentication app.

When 2FA is set up, users will need to:

• download a two-factor authentication app to their mobile device (e.g. Authy, Google Authenticator, Authenticator Plus, and others);

• use their device and the app to generate a token and log in.

If you’re an account owner (i.e. the user who created the Beefree SDK account), you may require all account users to use two-factor authentication to log in. To do so, go to the Setting & Security section in your personal area and enable Require two-factor authentication at login.

After saving the setting, you will be prompted to scan a QR code with a 2FA application to generate a security token to complete the setup.

When this setting is ON:

• every user will need to enter an authentication token, generated with a 2FA mobile app, to log into the account;

• when you create a new user, the 2FA toggle will be set to ON by default.

When adding or editing a user, you may also decide to turn on or off 2FA for that user, in order to:

• turn on 2FA, when 2FA is OFF at the account level;

• turn off 2FA, when 2FA is ON at the account level.

If 2FA is OFF at the account level, additional users, i.e. admins, can turn on 2FA for themselves, for their peace of mind. They can go to the “Profile” section of their personal area and turn it on.

Manage Subscriptions in the Console

We understand that each company has its own unique needs. For that reason, we offer the flexibility of adding multiple Beefree SDK subscriptions within the Developer Console. Through this option, you can take advantage of multiple subscriptions to our product for your teams, business units, and so on.

How to Add a New Subscription

You can create an additional subscription within the Beefree SDK Developer Console.

To achieve this, take the following steps:

1. Log in to the Beefree SDK Developer Console

2. Navigate to your dashboard

3. Click Add new subscription on the upper right-hand side of the screen

4. Type a name for your next subscription and click Next

5. Choose a plan and click Select plan

6. Confirm the plan you selected

7. Finalize your additional subscription

In the Toolbar Options tab you can:

• control individual settings that affect the top toolbar in the builder

• decide whether to hide the toolbar completely

The toolbar contains all the actions not related directly with content edition, like save, send a test or preview.

You can add favicons to email designs in the email builder. Adding a favicon directly to an email's HTML is beneficial when the email is viewed in a browser, and the end user would like a favicon to display in the browser tab.

When activated in the , a new Configure favicon option becomes available in the Settings tab of the builder, where end users can select or edit their favicon.

The following image shows an example of what this looks like in the builder.

The Favicon option is off by default and must be enabled in the .

Take the following steps:

Overview

The Rows endpoints help you keep templates consistent and avoid redundancy. Use them to list saved rows, apply updates across multiple templates, or retrieve synced rows.

Available Collection Values for Row Processing Endpoints

The following table lists the collection values available in this category of endpoints, and their corresponding collection options.

Prior to referencing the table, the following example shows how you can replace the {collection} placeholder.

How to Replace the {collection} Placeholder

The following example URL has a {collection} placeholder. This placeholder needs to be filled in with a Collection Option prior to making an API call.

https://api.getbee.io/v1/{collection}/merge-rows

As an example, if you'd like to merge rows for emails using this endpoint, replace {collection} with message.

The final URL to make the API call will be:

https://api.getbee.io/v1/message/merge-rows

The following table provides a comprehensive reference of all available options.

The merge method allows you to update a row across multiple templates. Specifically, it enables the host application to modify an element within an existing JSON document. This means you can implement a feature that updates templates in the background—without requiring any action from your users. It's ideal for merging shared content () into templates that use it—for example, updating the same footer across 30 different email or page templates.

URL: https://api.getbee.io/v1/{collection}/merge

URL: https://api.getbee.io/v1/{collection}/merge-rows

URL: https://api.getbee.io/v1/{collection}/synced-rows

What if a footer is shared by 10 messages and needs to be updated in all of them? The 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 index method in the Content Services API lets you retrieve a list of assets that include a specific saved row. This method is essential for determining which assets need to be updated using the merge method.

Typical Use Cases

• Updating shared headers or footers across multiple templates

• Modifying expiration dates in seasonal campaigns

• Applying price or link changes to reused promotional content

• Making any update to shared blocks without manually editing each message

Use the index method first to locate all impacted assets, then apply changes with the merge method to ensure content is updated consistently.

Overview

This page discusses how to use the HTML Importer API endpoint. Follow the instructions outlined in this page to successfully perform API calls.

Prerequisites

Prior to performing an API call, ensure the HTML you are using in the body of the POST request meets the following requirements:

• DOCTYPE declaration

• Include html and body elements

• To prevent character encoding issues during the conversion, include the <meta charset="UTF-8"> tag in the head section of your HTML before converting it.

Take the following steps to perform the conversion:

1. Ensure your API method is set to POST

2. Enter the endpoint URL: https://api.getbee.io/v1/conversion/html-to-json

   • Note: You can do this by setting {collection}

Within a few seconds, you should receive a response containing the Beefree JSON.

You can test the endpoint in the following interactive environment. Ensure you follow the steps outlined in the to successfully execute the API call after clicking the Test it button. You can copy and paste the HTML in the Sample HTML Template to Convert expandable section below, or use your own HTML as a request body for experimenting with the Test it feature.

Saved Rows Overview

This page provides an overview of Saved Rows and their key benefits.

What Are Saved Rows?

Saved Rows in Beefree SDK optimize the content creation process by allowing users to save, categorize, and manage reusable rows for future use. When this feature is enabled, users can simply click the Save icon on a row within their design and store it for later. This ensures quick access to preferred layouts and design elements across multiple projects.

Save Rows are particularly helpful in the following scenarios:

• Standardizing Footers: Save a footer row with contact details, social media links, and copyright information. Use it across multiple email templates to ensure consistency.

• Designing E-Commerce Product Grids: Create reusable rows showcasing product images, descriptions, and call-to-action buttons. Pull these rows dynamically from an e-commerce catalog for up-to-date content.

• Creating Promotional Banners: Save promotional rows with pre-configured styles and messaging. Reuse them across campaigns to maintain branding and reduce setup time.

There are several benefits to utilizing saved rows. This section outlines benefits for both end users and the host applications.

Saved Rows enable end users to:

• Save and reuse content: Create emails, landing pages, and popups, apply their own style and brand guidelines, and save all of that hard work inside of a row and reuse it at a later date. After saving a row, they can still edit the row and make any adjustments to the content blocks inside of it.

• Flexible Categorization: Organize rows into intuitive categories to easily find and reuse them later on.

• Easily Manage Rows: Edit the name and category of a saved row easily. Or, delete rows if they are no longer needed.

Saved Rows enable host applications to:

• Enhance the User Experience: Enable users to save, categorize, and manage rows efficiently.

• Multiple Storage Options: Activate, store, and manage Saved Rows using either or options.

• Customize Permissions: Enable or disable end user permissions to delete, edit, manage, or add Saved Rows.

When enabled, Saved Rows allow end users to select a row in their design and save it. This process involves:

1. Selecting a row in the builder.

2. Clicking the Save icon in the toolbar or row properties panel.

3. Storing the row’s structure, content, and styles as a JSON document in your chosen storage solution.*

Once created and saved, end users can reuse saved rows through the builder’s ROWS tab.

There, users can:

• Browse saved rows by category.

• Search for rows using metadata like row names or descriptions.

• Drag and drop rows into their designs for immediate use.

There are two paths you can take to activate and store Saved Rows for your application:

• : Enabled by default. Provides a storage solution and user interface.

• : Requires activation in the Beefree SDK console, along with creating your own endpoints to connect a database.

Both paths provide their own set of benefits and limitations. It is important to familiarize yourself with the benefits and limitations of each option to choose the storage and activation solution that is best for you and your application's needs. For more detailed information on both activation routes, reference and Implement .

Learn more about to discover the best option for you.

How it works

Our builders offer ready-to-go rows to your end-users, which provide both structure and content to create contents faster. With Edit Single Row mode you can offer an easier way for your users to modify a single row with a tailored UI built to edit the row structure, content, and style settings without worrying about messing up with the overall design of the email campaign, landing page, or pop-up.

Edit Single Row mode complements the Saved Rows as it allows a complete control over the content of individual rows (e.g. the footer that requires to be updated) without the need to intervene into a full template, this will help you in implementing a more effective way to manage libraries of Saved Rows with a streamlined design process.

Initializing the editor in Edit Single Row Mode

type ClientConfig = {
  workspace?: {
    editSingleRow?: boolean
    // ....
  }
  // ....
}

const beeConfig: ClientConfig = {
  workspace:{
    editSingleRow: true
    // ....
  }
  // ....
}


// Create the instance 
function BeePlugin.create(token, beeConfig, (beePluginInstance) => { 
  //.... 

  beePluginInstance.start(template, { shared: false })
}

When a builder application is initialized with this mode enabled the UI will show to the user only properties that pertain to editing a single row, therefore:

• the options to insert custom rows, saved rows, or new default rows are disabled,

• the Settings tab is unavailable, as those properties are specific to the entire document,

• when a row is selected on the editing stage, the action to Delete, Duplicate, Comment, Save are not available.

The following describes the recommended workflow to implement the Save action in your host SaaS application when the Single Edit Row mode is enabled.

In case your application uses the default , you can leverage the save button to trigger the sequence of action to correctly save the row. The workflow is the same as the one documented in , in short :

1. The user clicks on the save button

2. A contentDialog of type saveRow will be triggered.

In case your application doesn’t use the default Toolbar, you can now use the dedicated instance method to programmatically trigger the same row-saving flow as the default Save button:

• Call from your custom UI element.

• The callback will be triggered with the row JSON.

• Listening to the event. It will receive the updated full message JSON which again can be saved as a Saved Row.

An effective way to update saved rows across multiple templates is by in combination with the , to handle a row update across multiple existing templates.

Hosting Options Overview

Saved Rows in Beefree SDK empower users to save, reuse, and organize design elements efficiently, which optimizes the creation process for emails, pages, and popups. With Saved Rows, users can categorize rows by themes or criteria, ensuring easy access and consistency across projects.

Beefree SDK offers two hosting options: Hosted Saved Rows and Self-Hosted Saved Rows. Each option has unique advantages suited to specific organizational needs, resources, and technical requirements. This guide compares the options, helping you choose the best fit for your team.

Hosted Saved Rows

Hosted Saved Rows offers a fully managed solution, eliminating the need to set up and maintain backend systems. With this option, Beefree SDK handles storage, security, scaling, and updates, allowing your team to focus on delivering a great user experience. In addition to managing storage, this option also provides you with a ready-to-go user interface made available to your application's end users by default.

This ready-to-go UI enables application end users to:

• Save a row and make it available for reuse in the future

• Add new saved row categories to organize the rows they save

• Edit a saved row's existing name and category

• Delete a saved row

• Update existing saved rows with the option to save them as new saved rows

• Fully managed by Beefree SDK, and available by default for Core applications and above.

• Ideal for teams that want a quick setup without maintaining backend systems.

• Offers centralized storage, security, and reliability, while also providing a user interface to save and reuse rows within your application.

Self-Hosted Saved Rows gives teams complete control over how Saved Rows are stored, managed, and secured. This option is best for organizations with specific compliance or integration requirements, and those with the resources to manage backend systems effectively.

• Allows full control over where and how rows are stored.

• Suitable for teams with specific compliance or integration needs.

• Requires development resources for managing row storage, and creating a user interface to manage and reuse rows.

Both options allow end users to save and reuse rows on the frontend, but the best hosting option for your team will depend on your priorities concerning setup complexity, development resources (for storage and building a UI), and ongoing maintenance.

• Explore

• Explore

Overview

Your users will have the ability to rewind and fast-forward to any point in their recent edit history. Once Undo is enabled in the Beefree SDK Console, the application immediately begins tracking changes. Behind the scenes, this is accomplished via a new callback event – called onChange – which can also be used “stand-alone” without enabling Undo. No client-side configuration is required to use this feature. Continue reading to learn how to activate and use Undo. And if you can’t wait to try it yourself, you can immediately do so at beefree.io

How it works

When changes are detected, a compact Undo widget displays in the bottom left corner of the stage:

The widget displays 3 actions:

• Undo and Redo arrows that offer the classic pattern to move back and forth between changes.

• A history icon that expands a timeline of the latest changes:

The timeline allows the user to browse through the most recent changes.

All the steps display:

• An icon to identify the content element type (an image, text, etc.)

• A description of what changed, giving the new property value (if any)

• The exact time it happened

All these details provide enough information for users to understand what modification was applied, and, if desired, rewind the message to that state:

When the user selects a previous step, the content or row that triggered the history record displays as the selected item, providing further context.

The timeline for more recent changes is still available, allowing the user to move forward without losing any changes:

The Undo widget currently displays the last 15 edits in the timeline, but users can always rewind to the Message opened state to undo all changes since the message was initially opened in the builder.

We are also doing additional testing to see if the number of recent edits can be increased beyond 15 without negatively impacting the browser’s performance. We will update this section if the number is increased.

The last saved edits are only available at the session level, so they reset every time the builder is loaded. If you need to provide a complete message history, you can build a custom one based on the onSave and onChange events (see below).

The Undo option is available at the application level in the . Select your application from the list and open the Application configuration in the bottom-right. The option to enable this widget is available in the Services list:

The widget uses the information to work. However, it doesn’t need a client-side configuration for the callback: once Undo is enabled, the application starts tracking changes even if the is not set in .

Introduction

This page discusses the core concepts related to installing Beefree SDK within your application. These core concepts are the following:

• Installing the within your application.

• Understanding the Authorization process and how to successfully authenticate server-to-server.

• Adding the required to your application.

By the end of this guide, you'll understand the core concepts related to how you can install the package, authenticate, and get started with Beefree SDK. You'll have working a local environment set up on your machine to experiment with.

For a quick start, visit our , , and Quickstart guides, which each include complete sample code by framework.

Prior to integrating Beefree SDK, ensure you have completed the following:

1. Signed up for a account.

   1. within the Developer Console

   2. Obtained a Client ID and Client Secret for that application

This section covers the core concepts for installing Beefree SDK within your application and launching a local environment.

The concepts covered in this section are the following:

You can install Beefree SDK using either or :

Using npm

Using Yarn

Package Details:

• TypeScript Support: Included

• License: Apache-2.0

• Repository:

This section discusses the authentication process. It explains important concepts related to how to successfully authenticate using a server-to-server call.

The secure authentication flow requires a server-to-server call to obtain a JWT token. This process ensures your client credentials remain protected.

At a high level, the steps you need to take throughout the authentication process are the following:

1. Secure Credentials

   1. Never expose client_id or client_secret in frontend code.

   2. Store them in backend environment variables (.env

• Call Beefree SDK’s loginV2 and include the following required parameters:

  • client_id

  • client_secret

1. Frontend Handling

   1. Fetch token only from your proxy.

   2. Extract access_token from response.

The following table lists and describes the required authentication parameters.

Example Implementation (Node.js)

This section discusses how to initialize Beefree SDK.

Create a container element in your HTML where the editor will render:

Beefree SDK requires a configuration object with the required container property. are also available to customize the builder, but container is the only required one for initializing Beefree SDK.

The following code snippet shows an example of this:

Alternative approach:

The following table explains the container property.

Initialize the editor with a template JSON object:

Reference the in GitHub for example templates.

The following table lists template management methods that are important for getting started.

Implement automatic token refresh to maintain uninterrupted sessions:

How to use:

1. Get a fresh token from your backend

2. Pass it to updateToken()

Enable real-time collaboration with these additional methods:

How to use:

1. Generate a unique session-id on your server

2. Call join() with the same ID for all collaborators

Q: Can I use the SDK without server-side authentication? A: While possible for testing, production implementations must use server-side auth for security.

Q: How do I customize the editor's appearance? A: The SDK supports UI customization through . While the Configuration parameters provides a high level example, there are several configuration options outlined throughout the comprehensive technical documentation.

Q: What happens when the token expires? A: When your token expires after 12 hours:

1. The editor will become unresponsive

2. You must proactively:

3. Best practice is to refresh tokens before expiration (recommended at 11 hours)

Q: Where can I find sample templates? A: Visit our for examples.

This comprehensive guide covers all aspects of Beefree SDK integration, from initial setup to advanced features.

Remember to:

• Always use server-side authentication

• Implement proper token refresh logic

• Test thoroughly before production deployment

• Monitor for Beefree SDK updates and new features

Development Applications

Development applications are available with any Beefree SDK paid plan.

What is a Development Application?

A development application is a child application that is linked to your parent application within the Beefree SDK console. The purpose of these child applications is to create development, QA, or any other type of applications that you can merge your application’s changes to prior to pushing them to production. This empowers you to test new features, even on a higher plan, within a controlled environment prior to releasing them to your application’s end users.

How to Create a Development Application

You can create a development application within your Beefree SDK console. Prior to creating a development application, ensure you have a paid plan with Beefree SDK. Development applications are only available on paid plans.

To create a development application, take the following steps:

1. Log in to your

1. Create a new application

1. Navigate to your dashboard where the new application is located

2. Click the + next to Add a development instance

1. Type in the name of your development application, for example “development environment” or “QA environment”

1. Click Create

2. View the new development application available in your Beefree SDK dashboard

There are multiple benefits to utilizing development applications. A few of these benefits are the following:

• Merge and test changes to your application prior to releasing them to your end users.

• Create an environment for different contributors in your development cycle, for example QA Engineers, frontend developers, backend developers, and so on.

• Access next tier Beefree SDK features in your development applications.

Consider the information outlined in this section when working with development applications.

Beefree SDK lets you explore higher-tier features in your development environment for testing purposes. However, these features cannot be deployed to production unless they are included in your current subscription plan.

To use higher-tier features in production, you must .

Development apps inherit the same plan that your production app is on. If you wish to test features that are available on a higher plan, go the application details and click “CHANGE PLAN” in the upper right.

While setting up a development application is a feature on paid plans, please note that still apply. If, in your development application, you're using any of the Beefree SDK features that generate usage-based fees, that usage will count towards your plan's monthly allotment. You'll be charged usage-based fees if your usage (across production and development applications) exceeds your plan's allotment. . You can view usage statistics for your development applications by logging into the , locating the development application you are working with, and looking at the Statistics widget on the application details page.

Let’s start by looking at some of the peculiarities of the Popup builder.

In Email and Page Builder, the content area width is saved in the template. For example, if you start with an empty template, a default width that works for most scenarios is chosen, but the designer can adjust the message width slider. If you start with an existing template, the content width was chosen by the template’s designer using the message width slider in the builder Settings tab.

With Popup Builder, the same template may have multiple contexts, and each context will likely have specific size requirements. For example, an exit-intent popup may have a max-width of 600px on a desktop with a classical layout centered on the screen. On the other hand, the host app may display the same template on mobile in the bar style docked at the bottom of the screen with a restricted width of 300px.

Since the content area’s width is tightly coupled to the context and layout, no one size fits all width is saved in the template. Instead, the host app will specify the width settings when the builder loads, based on the context of using the template. Here is a quick example:

The following table provides an overview of the form fields that support the edit form field modal, including a description of each field and an example of its content.

Beefree SDK offers a comprehensive suite of features that enable your application's end users to save and manage reusable content. Rows are a core feature of the visual builders within Beefree SDK that provide end users with an intuitive avenue for saving and reusing content throughout their design creation workflows. They provide a structured method to house various types of content such as headers, paragraphs, images, and buttons.

Rows are also a fundamental part of how designs are built and structured within the visual builders. In the following GIF, you can see how each row functions as a component of a continuous design.

Rows allow end users to add multiples types of content to a section of a design. End users can either create their own rows from scratch (and save them for reuse on a later day), or they can use pre-designed rows that are pre-loaded into the host application and ready for use. Pre-loaded rows are helpful when providing a template structure that end users can customize as they build their designs.

Providing end users with the option to easily reuse content comes with a host of benefits, including:

Hosted Saved Rows offers a fully managed solution, eliminating the need to set up and maintain backend systems. With this option, Beefree SDK handles storage, security, scaling, and updates, allowing your team to focus on delivering a great user experience. In addition to managing storage, this option also provides you with a made available to your application's end users.

This enables application end users to:

• Save a row and make it available for reuse in the future.

• Add new saved row categories to organize the rows they save.

A CDN (Content Delivery Network) is a system of distributed servers that deliver web content, ensuring high availability and performance by distributing the service spatially relative to end-users. CDNs reduce load times, minimize latency, and enhance security for digital assets.

Beefree's Segmented CDN Infrastructure

If you rely on Beefree SDK storage, Beefree uses a segmented CDN infrastructure to serve your assets. We allocate distinct second-level domains per subscription tier and media type, and also assign you a dedicated third-level domain based on subscription ID.

This unique setup isolates your content from other SDK customers, mitigating risks from potential malicious or spammy uploads. By preventing one customer's actions from impacting others, Beefree ensures robust security and maintains the integrity and reputation of all digital assets.

When you create or manage an SDK application, your subscription plan determines which CDN domains your files use.

For free plans, all assets are served from the domain

In the , you'll find categories of Application Configurations you can customize to personalize your application. This page discusses the customization options available under the Privacy and Security section.

This category of Application Configurations enable you to customize the following:

• Anonymous error logging

• Custom limitation for the

Many digital marketing campaigns start with an attention-grabbing popup. In fact, many such campaigns include a popup, a landing page, and one or more emails.

• A cool popup highlights something that the reader may be interested in

• A landing page provides more information and includes some sort of signup form