Create Deployment
Creating a deployment with a deployment shape
Deployment shapes are pre-configured templates optimized for speed, cost, or efficiency. To create a deployment with a specific shape, pass thedeploymentShape field in the request body along with baseModel.
Use the Match Deployment Shape Versions endpoint to find available shapes for your model: it takes a deployment create request and returns the validated shape versions compatible with that model, ready to pass as deploymentShape.
activeModelVersion or targetModelVersion — the shape provides the necessary configuration.Always pass deploymentShape
Shapes are validated, so the hardware, precision, and serving configuration are known to work together. Omitting deploymentShape — whether or not you set acceleratorType, acceleratorCount, or precision — creates the deployment without a shape. Deployments without a shape are the most common cause of failed deployment creations, and the unshaped path may be deprecated in the future: always pass deploymentShape. See What is a deployment shape? for how to find shapes for your model.
Each model is validated only on the accelerator type, GPU count, and precision combinations covered by its shapes — many models support just one. Check Match Deployment Shape Versions before overriding acceleratorType or acceleratorCount: an unsupported combination typically fails at creation with a generic Internal error occurred message that does not name the hardware mismatch.Authorizations
Bearer authentication using your Fireworks API key. Format: Bearer <API_KEY>
Path Parameters
The Account Id
Query Parameters
By default, a deployment created with a currently undeployed base model will be deployed to this deployment. If true, this auto-deploy function is disabled.
By default, a deployment will use the speculative decoding settings from the base model. If true, this will disable speculative decoding.
The ID of the deployment. If not specified, a random ID will be generated.
If true, this will not create the deployment, but will return the deployment that would be created.
By default, a deployment will ensure the deployment shape provided is validated. If true, we will not require the deployment shape to be validated.
If true, skip the image tag policy validation that blocks certain image tags. This allows creating deployments with image tags that would otherwise be blocked.
Body
The properties of the deployment being created.
Human-readable display name of the deployment. e.g. "My Deployment" Must be fewer than 64 characters long.
Description of the deployment.
Deprecated: This field is deprecated and no longer causes auto-deletion. The time at which this deployment will automatically be deleted.
Annotations to identify deployment properties. Key/value pairs may be used by external tools or other services. Customer-managed keys supplied during deployment creation must begin with "custom/"; bare keys return HTTP 403 (PERMISSION_DENIED). See Deployment Tags for tag management and migration guidance. Responses to regular account users include only customer-owned tags with keys under the "custom/" prefix.
The minimum number of replicas. If not specified, the default is 0.
The maximum number of replicas. If not specified, the default is max(min_replica_count, 1). May be set to 0 to downscale the deployment to 0.
max_with_revocable_replica_count is max replica count including revocable capacity. The max revocable capacity will be max_with_revocable_replica_count - max_replica_count.
The number of accelerators used per replica. If not specified, the default is the estimated minimum required by the base model.
The type of accelerator to use.
ACCELERATOR_TYPE_UNSPECIFIED, NVIDIA_A100_80GB, NVIDIA_H100_80GB, AMD_MI300X_192GB, NVIDIA_A10G_24GB, NVIDIA_A100_40GB, NVIDIA_L4_24GB, NVIDIA_H200_141GB, NVIDIA_B200_180GB, AMD_MI325X_256GB, AMD_MI350X_288GB, NVIDIA_B300_288GB, NVIDIA_GB200, NVIDIA_GB300 The precision with which the model should be served.
PRECISION_UNSPECIFIED, FP16, FP8, FP8_MM, FP8_AR, FP8_MM_KV_ATTN, FP8_KV, FP8_MM_V2, FP8_V2, FP8_MM_KV_ATTN_V2, NF4, FP4, BF16, FP4_BLOCKSCALED_MM, FP4_MX_MOE The maximum number of concurrent (in-flight) requests a single replica will accept before shedding load. Requests that arrive while a replica is already at this limit are rejected early with HTTP 429 instead of queueing — a per-replica admission gate for controlling tail latency. When unset (0), the platform default is used.
If true, PEFT addons are enabled for this deployment.
The number of candidate tokens to generate per step for speculative decoding. Default is the base model's draft_token_count. Set CreateDeploymentRequest.disable_speculative_decoding to false to disable this behavior.
The draft model name for speculative decoding. e.g. accounts/fireworks/models/my-draft-model If empty, speculative decoding using a draft model is disabled. Default is the base model's default_draft_model. Set CreateDeploymentRequest.disable_speculative_decoding to false to disable this behavior.
The length of previous input sequence to be considered for N-gram speculation.
Whether to apply sticky routing based on user field.
Serverless will be set to true when creating deployment.
The set of API keys used to access the direct route deployment. If direct routing is not enabled, this field is unused.
If set, this deployment will expose an endpoint that bypasses the Fireworks API gateway.
DIRECT_ROUTE_TYPE_UNSPECIFIED, INTERNET, GCP_PRIVATE_SERVICE_CONNECT, AWS_PRIVATELINK The name of the deployment template to use for this deployment. Only available to enterprise accounts.
The performance profile to use for this deployment.
The desired geographic region where the deployment must be placed. If unspecified, the default is the GLOBAL multi-region.
The maximum context length supported by the model (context window). If set to 0 or not specified, the model's default maximum context length will be used.
Whether the deployment size validation is disabled.
Whether to use hot load for this deployment.
BUCKET_TYPE_UNSPECIFIED, MINIO, S3, NEBIUS, FW_HOSTED Allows up to 1 addon at a time to be loaded, and will merge it into the base model.
The name of the deployment shape that this deployment is using. On the server side, this will be replaced with the deployment shape version name.
The model version that is currently active and applied to running replicas of a deployment.
The target model version that is being rolled out to the deployment. In a ready steady state, the target model version is the same as the active model version.
Optional pricing plan ID for custom billing configuration. If set, this deployment will use the pricing plan's billing rules instead of default billing behavior.
Controls hot-load reload semantics for this deployment. ASYNC (default when enable_hot_load is set) pauses the generator/prefiller mid-flight and skips draining in-flight requests during hot load. SYNC drains in-flight requests before applying the new model.
HOT_LOAD_TRANSITION_TYPE_UNSPECIFIED, ASYNC, SYNC When true, this deployment runs as preemptible.
Response
A successful response.
Human-readable display name of the deployment. e.g. "My Deployment" Must be fewer than 64 characters long.
Description of the deployment.
The creation time of the deployment.
Deprecated: This field is deprecated and no longer causes auto-deletion. The time at which this deployment will automatically be deleted.
The time at which the resource will be hard deleted.
The time at which the resource will be soft deleted.
The state of the deployment.
STATE_UNSPECIFIED, CREATING, READY, DELETING, FAILED, UPDATING, DELETED Detailed status information regarding the most recent operation.
Annotations to identify deployment properties. Key/value pairs may be used by external tools or other services. Customer-managed keys supplied during deployment creation must begin with "custom/"; bare keys return HTTP 403 (PERMISSION_DENIED). See Deployment Tags for tag management and migration guidance. Responses to regular account users include only customer-owned tags with keys under the "custom/" prefix.
The minimum number of replicas. If not specified, the default is 0.
The maximum number of replicas. If not specified, the default is max(min_replica_count, 1). May be set to 0 to downscale the deployment to 0.
max_with_revocable_replica_count is max replica count including revocable capacity. The max revocable capacity will be max_with_revocable_replica_count - max_replica_count.
The desired number of replicas for this deployment. This represents the target replica count that the system is trying to achieve.
The number of accelerators used per replica. If not specified, the default is the estimated minimum required by the base model.
The type of accelerator to use.
ACCELERATOR_TYPE_UNSPECIFIED, NVIDIA_A100_80GB, NVIDIA_H100_80GB, AMD_MI300X_192GB, NVIDIA_A10G_24GB, NVIDIA_A100_40GB, NVIDIA_L4_24GB, NVIDIA_H200_141GB, NVIDIA_B200_180GB, AMD_MI325X_256GB, AMD_MI350X_288GB, NVIDIA_B300_288GB, NVIDIA_GB200, NVIDIA_GB300 The precision with which the model should be served.
PRECISION_UNSPECIFIED, FP16, FP8, FP8_MM, FP8_AR, FP8_MM_KV_ATTN, FP8_KV, FP8_MM_V2, FP8_V2, FP8_MM_KV_ATTN_V2, NF4, FP4, BF16, FP4_BLOCKSCALED_MM, FP4_MX_MOE The maximum number of concurrent (in-flight) requests a single replica will accept before shedding load. Requests that arrive while a replica is already at this limit are rejected early with HTTP 429 instead of queueing — a per-replica admission gate for controlling tail latency. When unset (0), the platform default is used.
If set, this deployment is deployed to a cloud-premise cluster.
If true, PEFT addons are enabled for this deployment.
The number of candidate tokens to generate per step for speculative decoding. Default is the base model's draft_token_count. Set CreateDeploymentRequest.disable_speculative_decoding to false to disable this behavior.
The draft model name for speculative decoding. e.g. accounts/fireworks/models/my-draft-model If empty, speculative decoding using a draft model is disabled. Default is the base model's default_draft_model. Set CreateDeploymentRequest.disable_speculative_decoding to false to disable this behavior.
The length of previous input sequence to be considered for N-gram speculation.
Whether to apply sticky routing based on user field.
Serverless will be set to true when creating deployment.
The set of API keys used to access the direct route deployment. If direct routing is not enabled, this field is unused.
If set, this deployment will expose an endpoint that bypasses the Fireworks API gateway.
DIRECT_ROUTE_TYPE_UNSPECIFIED, INTERNET, GCP_PRIVATE_SERVICE_CONNECT, AWS_PRIVATELINK The handle for calling a direct route. The meaning of the handle depends on the direct route type of the deployment: INTERNET -> The host name for accessing the deployment GCP_PRIVATE_SERVICE_CONNECT -> The service attachment name used to create the PSC endpoint. AWS_PRIVATELINK -> The service name used to create the VPC endpoint.
The name of the deployment template to use for this deployment. Only available to enterprise accounts.
The performance profile to use for this deployment.
The desired geographic region where the deployment must be placed. If unspecified, the default is the GLOBAL multi-region.
The geographic region where the deployment is presently located. This region may change
over time, but within the placement constraint.
REGION_UNSPECIFIED, US_IOWA_1, US_VIRGINIA_1, US_VIRGINIA_2, US_ILLINOIS_1, AP_TOKYO_1, US_ARIZONA_1, US_TEXAS_1, US_ILLINOIS_2, EU_FRANKFURT_1, US_TEXAS_2, EU_ICELAND_1, EU_ICELAND_2, US_WASHINGTON_1, US_WASHINGTON_2, US_WASHINGTON_3, AP_TOKYO_2, US_CALIFORNIA_1, US_UTAH_1, US_ARIZONA_3, US_GEORGIA_1, US_GEORGIA_2, US_WASHINGTON_4, US_GEORGIA_3, NA_BRITISHCOLUMBIA_1, US_GEORGIA_4, US_OHIO_1, US_NEWYORK_1, EU_NETHERLANDS_1, US_WASHINGTON_5, US_MINNESOTA_1, US_CALIFORNIA_2, NA_BRITISHCOLUMBIA_2, AP_MALAYSIA_2, US_OREGON_1, NA_BRITISHCOLUMBIA_3, AP_NEWSOUTHWALES_1, AP_TAIWAN_1 The maximum context length supported by the model (context window). If set to 0 or not specified, the model's default maximum context length will be used.
The update time for the deployment.
Whether the deployment size validation is disabled.
Whether to use hot load for this deployment.
BUCKET_TYPE_UNSPECIFIED, MINIO, S3, NEBIUS, FW_HOSTED Allows up to 1 addon at a time to be loaded, and will merge it into the base model.
The name of the deployment shape that this deployment is using. On the server side, this will be replaced with the deployment shape version name.
The model version that is currently active and applied to running replicas of a deployment.
The target model version that is being rolled out to the deployment. In a ready steady state, the target model version is the same as the active model version.
Per-replica deployment status counters. Provides visibility into the deployment process by tracking replicas in different stages of the deployment lifecycle.
Optional pricing plan ID for custom billing configuration. If set, this deployment will use the pricing plan's billing rules instead of default billing behavior.
Controls hot-load reload semantics for this deployment. ASYNC (default when enable_hot_load is set) pauses the generator/prefiller mid-flight and skips draining in-flight requests during hot load. SYNC drains in-flight requests before applying the new model.
HOT_LOAD_TRANSITION_TYPE_UNSPECIFIED, ASYNC, SYNC When true, this deployment runs as preemptible.