Match Deployment Shape Versions
Returns the deployment shape versions compatible with the provided deployment create request. Use this to discover a validated shape before creating a deployment with deployment_shape set - shapeless deployments (raw accelerator type/count) skip validated-configuration checks and are far more likely to fail at creation.
createDeploymentRequest.deployment.baseModel — and the response returns the latest validated shape versions that can serve that model, ready to pass as deploymentShape.
Match applies the full server-side compatibility logic for you: PEFT base-model resolution (for LoRA addons and live merge, shapes are matched against the PEFT base model), model-type and parameter-count tiers, embedding vs. non-embedding models, the MULTI_LORA capability gate when enableAddons is set, and hiding of FP4 shapes for full-parameter fine-tunes. List Deployment Shape Versions only lists versions of a shape you already know and cannot answer “which shapes work with this model?” — use Match for that.
accounts/fireworks fails with a permission error). The model in the request body, however, can live in any account you can deploy from, including publisher accounts like accounts/fireworks; public shapes from the publisher’s account flow into the results.Example: Match shapes for a model
enableAddons in the request — only shapes with the MULTI_LORA capability are returned:
deploymentShape in the Create Deployment request. See What is a deployment shape? for why you should always create deployments from a shape.Authorizations
Bearer authentication using your Fireworks API key. Format: Bearer <API_KEY>
Path Parameters
The Account Id
Body
The deployment create request to match deployment shape versions for.
The deployment create request to match deployment shape versions for. The full CreateDeploymentRequest schema is accepted here — including fields like deployment.enableAddons that affect shape compatibility — only the most common fields are listed below. See the Create Deployment reference page for the complete request schema.
Response
A successful response.
A token, which can be sent as page_token to retrieve the next page.
If this field is omitted, there are no subsequent pages.
The total number of deployment shape versions.