Setka Editor API Integration Introduction to Custom Integration

Introduction to Custom Integration

Aside from Wordpress, Setka Editor plugin can be integrated with other CMS: Joomla, Drupal, 1CBitrix, Typo3, etc.

Setka Editor is a WYSIWYG editor for online publications and blogs. It allows to establish a regular prompt release of beautiful and complex posts without any involvement of layout specialists and without pre-creation of layouts. Setka Editor consists of two parts:

  • JS editor built into the post editing page in CMS
  • Style Manager – a web interface at for creating and editing a branded style of a publication. It allows to create post styles (fonts, headings, colors) and grids (setting parameters for columns, indents and spaces between columns).

Integration of Setka Editor and CMS is carried out in two stages:  

  1. Integration with Style Manager for updating the editor and styles from the Style Manager account
  2. Initializing the Setka Post Editor on the CMS post editing page


Account registration and completion

To start integration you have to create an account (if you don’t have it yet) at Fill in all required fields and contact us to activate fields for a custom integration in your account, so you will be able to provide us with urls to your server.


What is required for integration:

  1. Enter the license key. You may find the license key in your personal account. To activate your subscription you need to create a field in your CMS for entering the license key. It is not necessary to create a field in the interface, you can add it in the code only.
  2. Fill in all the fields* in the Integration tab.

Editor config url - to receive and process updates of the styles created in the Style Manager in your CMS.

Company status url  - contains subscription information: whether a payment has passed or not, end of the trial period, etc.

Server status url - client information.

Local hostnames (localhost, will not be accepted. Domain name should be delegated to DNS-servers and resolve into public IP-address.




For correct integration all the links must be entered in accordance with the protocol (http/https).

The latest version of the API documentation is available at:

Ruby on Rails Examples:


Custom integration: