Version 2.0.12

New Major functionality is added in this version of ReadyCMS regarding headless fields, new endpoints and staging environments.

1. Headless Fields

New Major functionality is added in this version of ReadyCMS. 

From now on, administrators can create additional content fields as part of this initial headless functionality.

Version 2.0.12-0

Every Content Type, including eCommerce content types, can benefit from this functionality.

New field types that can be managed are:

  1. Text
  2. Number
  3. Email
  4. Checkbox
  5. Date
  6. Month
  7. Password
  8. URL
  9. Textarea
All headless fields can be grouped by adding the group name. Group name is transformed to a key value that is used in the API.

Example 1: Additional fields can be used as a way to control additional section on the website:

Version 2.0.12-1
Version 2.0.12-2

Please consult our API documentation if you are a developer.

2. API endpoint / Count

New endpoint /count/ is added for all major content groups.


These endpoints can be filtered as their main parent endpoint. Result is the number of items. 
Number of filtered items can also be found in other endpoints as a part of [‘data’][‘pagination’][‘total’] value.

{ "data": { "count": "11544" }, "http_request": { "REMOTE_ADDR": "", "HTTP_REFERER": "", "HTTP_ORIGIN": "" } }

3. API Development Environment

Both admin instance and the API service are extended to support development environments.

In ReadyCMS you can have four development environments:

  • Production - Default environment
  • Staging
  • Testing
  • Development

It is important to mention that Media and Settings are not affected by the change of the development environment.

If you are a developer, changing the environment can be easily done by sending the “environment” variable to the API. 

&environment="dev" // For Development environment
&environment="test" // For Testing environment
&environment="stage" // For Staging environment
&environment="prod" // This is optional, you don't need to send this variable since production environment is a default option

API Development Environments are not enabled by default in any of the current subscription plans. To activate this option, contact our sales team via one of our support channels.

Help us improve our documentation

Suggest changes or request new documentation

Suggest changes