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
- Identify the templateId of the Email Builder template you want to modify.
- Create a JSON payload that includes editorType and editorContent, adding any optional fields such as subject, fromName, fromEmail, or previewText that need to change.
- Send a PATCH request to the endpoint PATCH /emails/builder/:templateId with the payload and the required authentication.
- 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
- Select the appropriate API version before making requests. API version selection
- Explore other developer tools and resources offered by HighLevel. All developer resources
- Review pricing and plan eligibility for API access. Pricing and plans
Michael's take

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.