Skip to main content
PATCH
cURL
Use autoscaling_schedule_settings to manage autoscaling schedules: recurring daily or hourly windows, and one-time windows for planned events like launches and load tests. For organizations with mixed mode rolling deployments (beta) enabled, promotion_settings.rolling_deploy_config accepts non-zero values for both max_surge_percent and max_unavailable_percent. Omitted promotion settings retain their current values. Set the budget you want to disable to 0. Changes apply to future promotions; confirm the saved values in the response’s environment.promotion_settings.rolling_deploy_config.

Authorizations

Authorization
string
header
required

Send Authorization: Bearer <api_key>. The legacy Authorization: Api-Key <api_key> scheme is also accepted.

Path Parameters

model_id
string
required
env_name
string
required

Body

application/json

A request to update an environment.

autoscaling_settings
UpdateAutoscalingSettingsV1 · object | null

Autoscaling settings for the environment

Example:
promotion_settings
UpdateModelPromotionSettingsV1 · object | null

Promotion settings for the environment

Example:
autoscaling_schedule_settings
UpdateAutoscalingScheduleSettingsV1 · object | null

Partial autoscaling schedule collection update. Omitted collection fields and existing schedules are unchanged; each submitted schedule is a complete create or replacement.

Example:
request_backpressure_settings
UpdateRequestBackpressureSettingsV1 · object | null

Request backpressure settings for the environment.

Example:
traffic_routing_settings
UpdateTrafficRoutingSettingsV1 · object | null

Partial traffic routing rule update. Each submitted rule is a complete create or replace. Deletes are applied first. In development.

Example:

Response

200 - application/json

The response to a request to update an environment's settings.

environment
EnvironmentV1 · object
required

The environment after the update, matching the shape returned by GET.

status
enum<string>
required
deprecated

Deprecated. Kept for legacy autoscaling-only update operation behavior.

Available options:
ACCEPTED,
QUEUED,
UNCHANGED
message
string
required
deprecated

Deprecated. Kept for legacy autoscaling-only update operation behavior.