I'm building a migration tool using the GHL API and have identified a critical gap in the Email Builder API endpoints. While the API supports creating templates with type: "builder", there's currently no way to retrieve the editorData (or dnd) JSON structure that defines Design Editor templates.

Current API Behavior:

GET /emails/builder - Returns template metadata only (name, type, previewUrl) but not editorData

GET /emails/builder/{templateId} - Returns 404 (endpoint doesn't exist in public API)

GET /emails/builder/data?templateId=X&locationId=Y - Returns 404

POST /emails/builder/data - Accepts editorData for updates but provides no GET equivalent

Issue:

The only way to obtain the editorData structure is through GHL's internal backend endpoints (e.g., backend.leadconnectorhq.com/emails/builder/data/{locationId}/{templateId}), which require browser session authentication and aren't accessible via OAuth or Private Integration API tokens.

Request:

Please add a public API endpoint to retrieve complete email template data including the editorData JSON structure, for example:

GET /emails/builder/{templateId}?includeEditorData=true

Or extend the existing list endpoint to optionally return editorData

Use Case:

This would enable legitimate migration tools, backup solutions, and template management applications to preserve Design Editor templates in their native format rather than falling back to HTML-only representation.

Current Workaround:

Templates can only be migrated by importing the preview HTML via templateDataUrl, which creates them as Code Editor (HTML) type rather than preserving the original Design Editor format with drag-and-drop editing capability.

Is this intentionally restricted? Any guidance would be appreciated.