All the code of every email template should be stored within your DB.
When your customer decides to modify any of the email templates, he clicks on it, and you pass the HTML and CSS of that clicked template to the editor.
Suppose an auto-saving feature is activated and configured. In that case, all changes made in the email template will trigger the request to our end with micropatches (those particular changes) in order to save them in our DB.
As soon as they are saved, our server will send the request to specified by your end-point with the full changed HTML and CSS to replace the old version with a new one in your DB.
If this feature is not activated, then a user has to click on the "Save" button manually within your app, and you should call the "getTemplate" function to take out modified HTML and CSS from the editor in order to save it within your DB.
Please find more information about the "getTemplate" function following this link.
Enable the "AutoSave" option on the Plugin details page to receive a fresh version of the HTML and CSS code to your backend every time a change has been done by a user in the editor.
*Please notice that it's available only for paid packages.
To support this option, you need to implement the interface on your backend that will receive the calls:
"Response status": "200 OK"
Please take a look at the descriptions of the request parameters below:
The Basic Authentication is used to send these requests, so please make sure that you have specified the correct Login, Password, and API URL in the Stripo Plugin.
Thank you for taking the time to read our articles. We hope you will find this information helpful.
If you have any additional questions, please email us at email@example.com.
We would be glad to talk with you.