Home/HighLevel/Features/Developer Resources/Patch Email Builder templates with HighLevel API

Agency, Settings and Integrations

Patch Email Builder templates with HighLevel API

In short

The Email Builder Template Update API lets developers change an existing template’s design and its email settings, subject, sender name, sender address, and preview text, through a single PATCH request. It streamlines programmatic edits without opening the HighLevel UI.

AreaDeveloper Resources · Developer Resources
Used forMarketing agency, SaaS product, Integration partner
Setup steps4 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agencies that build and maintain many client email templates can keep designs consistent via code.
  • Developers integrating HighLevel into external platforms can automate content updates without manual steps.

02Email template update API, explained

The endpoint PATCH /emails/builder/:templateId updates an existing Email Builder template identified by its templateId. You can send a JSON payload that contains the simplified editor fields editorType and editorContent, plus any of the optional email settings such as subject, fromName, fromEmail, and previewText. All fields are optional, so the request can target just content, just settings, or both.

When the request succeeds, HighLevel replaces the template’s content and the supplied settings while preserving any unchanged fields. The platform automatically derives the plain text version, so isPlainText does not need to be provided. This behavior mirrors the manual edit experience but occurs via API.

The endpoint lives in the HighLevel developer API suite. It does not affect campaigns that have already been sent, scheduled, or copied into workflow steps unless those copies are synchronized with the original template. After calling the API, you should open the template in HighLevel to verify the changes and preview the email.

03How businesses use email template update API

  • Marketing agency. The agency builds a script that loops through client template IDs, constructs a payload with new HTML content and updated subject lines, then sends a PATCH request for each. This keeps client branding up to date without logging into each account.
  • SaaS product. The product generates personalized onboarding emails by updating a single shared template’s previewText and fromName via the API whenever a new company signs up. The integration sends a PATCH call with those fields while leaving the body unchanged.
  • Integration partner. The partner’s platform syncs template content from an external design tool. When designers export HTML, the platform builds a payload with editorType set to "html" and editorContent containing the markup, then issues a PATCH request to overwrite the HighLevel template.

04The numbers and rules that matter

  • Supported email settings: Subject, fromName, fromEmail, previewText.

05How to set up and use email template update API in HighLevel

Update an existing Email Builder template through the API

  1. Identify the templateId of the Email Builder template you want to modify.
  2. Create a JSON payload that includes editorType and editorContent, adding any optional fields such as subject, fromName, fromEmail, or previewText that need to change.
  3. Send a PATCH request to the endpoint PATCH /emails/builder/:templateId with the payload and the required authentication.
  4. Open the template in HighLevel, review the updated content and settings, and preview the email to confirm the changes.

06Settings that matter

  • subject. Controls the line shown in the recipient’s inbox.
  • fromName. Sets the sender name displayed to the recipient.
  • fromEmail. Specifies the sender email address and is validated for proper format.
  • previewText. Defines the short snippet shown near the subject line in many inboxes.
  • editorType. Indicates the type of editor content being sent, such as "html".
  • editorContent. Contains the actual HTML markup or design markup for the email body.

07Things to know before you rely on it

  • The endpoint updates only the stored Email Builder template; it does not modify sent or scheduled campaigns.
  • Workflow steps that contain a copied version of the template may not reflect the changes unless the step is synced with the original template.
  • All fields in the request are optional; only supplied fields are altered.
  • isPlainText is generated automatically and should not be included in the payload.

08If something goes wrong

  • Invalid fromEmail format causes the request to fail validation.. Provide a correctly formatted email address for the fromEmail field.
  • Template changes are not visible in a workflow email.. Verify that the workflow email step is synced with the original template and test the step after the API update.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

The problem many agencies face is keeping dozens of email templates in sync with brand changes and new copy without opening each one in the UI. The Email Template Update API can reduce that manual work by letting you push content and inbox settings in one request.

If you include a fromEmail value, make sure it is a valid email address to avoid validation errors that could halt the update.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about email template update API.

Can I update only the subject line without changing the template content?

Yes. All email settings fields are optional, so you can send just the subject field in the request.

Is the fromEmail field validated?

Yes. The API checks that fromEmail follows a proper email format and will reject the request if it does not.

Do I need to include isPlainText in the payload?

No. The simplified payload automatically derives isPlainText, so you should omit that field.

Will this endpoint update templates that have been copied into workflow steps?

Not always. Workflow emails may use a copied version; you need to confirm synchronization and test after updating.

Can I update both the design and the email settings in the same request?

Yes. The endpoint accepts editorType, editorContent, and any of the optional settings together in a single PATCH call.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.