Skip to content
v1.0.0
OpenAPI 3.0.3

Email Model Clone API

This API method allows you to clone an existing email model and create a new one based on its structure and content.

The cloned email model is created as a separate entity with a new identifier, while the original email model remains unchanged.

This method is useful when you need to duplicate an email model programmatically and continue working with the copied version independently.

Server:https://plugins.stripo.email

Stripo API server

Client Libraries

Methods

​

Clone email model

​

Clone an existing email model and create a new email model based on it.

The method copies the structure and content of the source email model and creates a new email model with a new unique identifier.

The response contains the identifier of the newly created email model, which can be used for further operations in the editor or via API.

To copy a specific historical version of the source email, pass the optional patchId — see the Restore a Version as a New Email guide.

Headers

  • Stripo plugin auth token in the format - Bearer ${AUTH_TOKEN}

  • JSON string with parameters to identify email (same as metadata parameter in the UI editor). For example: {"emailId": "id1"}

Body·

required
application/json
  • Destination email ID

  • Optional. UUID of a version (patch) of the source email. When provided, the destination model is created from the content of this historical version instead of the current state of the source model. The value must identify a visible, non-technical version of the source email -- an invalid, unknown, foreign, hidden, or technical patchId returns 400 Bad Request and the destination model is not created. The initial version ID 00000000-0000-0000-0000-000000000001 is supported. Note: if the source email uses a Template Theme, the destination is bound to the latest version of that theme -- the historical theme state is not restored.

  • Source email ID

Responses

  • Email model cloned successfully. Returns the ID of the newly created email model.

    • Destination email ID

    application/json
Request Example for post/coediting/v1/email/copy
curl https://plugins.stripo.email/coediting/v1/email/copy \
  --request POST \
  --header 'ES-PLUGIN-AUTH: ' \
  --header 'ES-PLUGIN-UI-DATA: ' \
  --header 'Content-Type: application/json' \
  --data '{
  "sourceId": "",
  "destinationId": "",
  "patchId": null
}'
{
  "destinationId": "string"
}

Models

​
  • Destination email ID

  • Optional. UUID of a version (patch) of the source email. When provided, the destination model is created from the content of this historical version instead of the current state of the source model. The value must identify a visible, non-technical version of the source email -- an invalid, unknown, foreign, hidden, or technical patchId returns 400 Bad Request and the destination model is not created. The initial version ID 00000000-0000-0000-0000-000000000001 is supported. Note: if the source email uses a Template Theme, the destination is bound to the latest version of that theme -- the historical theme state is not restored.

  • Source email ID

​
  • Destination email ID