WordPress Site Environments

The available WordPress site environments include:

• Live
• Staging
• Premium Staging

Using the environments endpoint, you can:

• Get information about your site’s environments.
• Create a new environment (with or without WordPress).
• Push an environment
• Clone an existing environment.
• Delete an environment.

You can obtain the site_id using the GET request with the WordPress Sites endpoint.

The site_id is also shown in the URL in MyKinsta when you access the environment, for example in the URL https://my.kinsta.com/sites/details/fbab4927-e354-4044-b226-29ac0fbd20ca/c84ce214-69b9-4a32-8e67-880672cf1d38?idCompany=bdd25d71-5706-4890-870f-1adda17c505d:

• The site_id is fbab4927-e354-4044-b226-29ac0fbd20ca
• The environment_id is c84ce214-69b9-4a32-8e67-880672cf1d38
• The company_id is bdd25d71-5706-4890-870f-1adda17c505d

The change-environment-php-allocation and change-site-php-allocation endpoints are not currently available to customers who have the PHP memory add-on or those on any of following plans: Single 1.25M or above, WP 60 or above, Agency, or a custom plan.

The PHP memory limit and number of PHP threads must add up to the existing total memory pool of the site. You can only change the total memory pool within PHP performance in MyKinsta.

change-environment-php-allocation can only be used for premium staging environments.

change-site-php-allocation updates the PHP memory limit of the live environment and all standard staging environments. Strandard staging environments will always have 2 PHP threads regardless of their memory allocated. You cannot use this endpoint to update premium staging environments.