Create environment
Approval settings
You cannot configure approval settings when you create a new environment. Use Update environment to update approval settings.
The
approvalSettingsandresourceApprovalSettingskeys are only returned when the approvals feature is enabled.
Create a new environment in a specified project with a given name, key, swatch color, and default TTL.
Authorizations
Path Parameters
The project key
Body
A human-friendly name for the new environment
"My Environment"
A project-unique key for the new environment
"environment-key-123abc"
A color to indicate this environment in the UI
"F5A623"
The default time (in minutes) that the PHP SDK can cache feature flag rules locally
5
Ensures that one end user of the client-side SDK cannot inspect the variations for another end user
true
The initial value of trackEvents for flags created in this environment. Does not affect existing flags. Required for Data Export, but doesn't enable Data Export on its own.
false
Requires confirmation for all flag and segment changes via the UI in this environment
false
Requires comments for all flag and segment changes via the UI in this environment
false
Tags to apply to the new environment
Indicates that the new environment created will be cloned from the provided source environment
Whether the environment is critical
true
Response
Environment response
The location and content type of related resources
The ID for the environment. Use this as the client-side ID for authorization in some client-side SDKs, and to associate LaunchDarkly environments with CDN integrations in edge SDKs.
"57be1db38b75bf0772d11384"
A project-unique key for the new environment
"environment-key-123abc"
A human-friendly name for the new environment
"My Environment"
The SDK key for the environment. Use this for authorization in server-side SDKs.
"sdk-xxx"
The mobile key for the environment. Use this for authorization in mobile SDKs.
"mob-xxx"
The color used to indicate this environment in the UI
"F5A623"
The default time (in minutes) that the PHP SDK can cache feature flag rules locally
5
Ensures that one end user of the client-side SDK cannot inspect the variations for another end user
true
The initial value of trackEvents for flags created in this environment. Does not affect existing flags. Required for Data Export, but doesn't enable Data Export on its own.
false
Whether members who modify flags and segments through the LaunchDarkly user interface are required to add a comment
true
Whether members who modify flags and segments through the LaunchDarkly user interface are required to confirm those changes
true
A list of tags for this environment
Whether the environment is critical
true
Details about the approval settings for flags in this environment
Details about the approval settings for other resources in this environment, organized by resource kind (for example, "aiconfig" and "segment")