v1
latestOpenAPI 3.1.02026-07-26106201349.6 KBCreate Deployment
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.
Request body
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.
- CREATING: The deployment is still being created.
- READY: The deployment is ready to be used.
- DELETING: The deployment is being deleted.
- FAILED: The deployment failed to be created. See the status field for additional details on why it failed.
- UPDATING: There are in-progress updates happening with the deployment.
- DELETED: The deployment is soft-deleted.
Annotations to identify deployment properties. Key/value pairs may be used by external tools or other services. The "image-tag-reason" key is redacted from API responses for non-superuser principals.
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 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.
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 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.
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.
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.
- CREATING: The deployment is still being created.
- READY: The deployment is ready to be used.
- DELETING: The deployment is being deleted.
- FAILED: The deployment failed to be created. See the status field for additional details on why it failed.
- UPDATING: There are in-progress updates happening with the deployment.
- DELETED: The deployment is soft-deleted.
Annotations to identify deployment properties. Key/value pairs may be used by external tools or other services. The "image-tag-reason" key is redacted from API responses for non-superuser principals.
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 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.
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 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.
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.
When true, this deployment runs as preemptible.