This guide concerns teams choosing to evaluate another endpoint. The current documentation labels v1.6 Stable and Try-On Max Preview. It does not establish that a working v1.6 integration must be retired.
Diagnose the migration as a schema change
A merchant may have a working v1.6 integration and want to evaluate Try-On Max for a new catalog. The familiar request wrapper can make the migration look trivial. Both endpoints use FASHN's general request structure, but the meaning and accepted names of the fields inside inputs are endpoint-specific.
Start with a saved example of the existing v1.6 request, without credentials. Identify which values are actual images, which select a garment category, and which govern generation behavior. Then open the Try-On Max schema and create a new request specification rather than copying every old field.
FASHN documents product_image and model_image for Max, with an optional prompt for limited wearing or styling instructions. Its supported product scope includes clothing and wearable accessories. That does not make v1.6 category behavior a universal control for Max.
Map responsibilities before renaming fields
| v1.6 request field | Max comparison |
|---|---|
| model_name: tryon-v1.6 | model_name: tryon-max |
| inputs.garment_image | inputs.product_image |
| inputs.model_image | Retain the intended model_image input |
| inputs.category | Not a documented Max input; do not copy it |
| inputs.mode | Choose an explicit permitted generation_mode; do not copy performance as a Max value |
| inputs.num_samples | Review intended output count against Max num_images |
In v1.6, garment_image identifies the garment reference. In Max, product_image represents the item being placed on the person. The target model image remains a separate input. The migration should preserve those semantic responsibilities even though the parameter names differ.
Do not blindly rename a category such as tops into an imagined Max field. If the old workflow relied on category to restrict a top-only replacement, that expectation must become an explicit review requirement. An optional natural-language instruction may help describe the intended styling, but it should not be represented as a guaranteed replacement for v1.6 category selection.
Review every additional setting against the Max reference. A field accepted by one endpoint is not automatically supported by another. This matters especially when an application constructs requests by merging a shared configuration object with endpoint-specific inputs.
Illustrative comparison: the same jacket task
A fictional fashion retailer has a v1.6 jacket workflow and now wants to evaluate Max for the same jacket presentation. Its old request template contains garment_image, model_image, category, and a mode setting.
For the jacket comparison, the seller should build a Max-specific request using the same jacket photograph as product_image and the intended model photograph as model_image. The old category field should not be carried forward merely because the integration has a default value.
| Old request responsibility | Max migration decision |
|---|---|
| Garment source in garment_image | Map the intended wearable item to product_image |
| Target person in model_image | Retain the correct model-image responsibility |
| v1.6 category | Remove from the Max request; define the intended change separately |
| Generation settings | Check each name and permitted value against Max documentation |
| Old expected output | Define a new Max-specific acceptance review |
This is an illustrative migration plan, not a submitted request or observed result.
Use error location to select the repair
If the actual returned validation details identify an unknown or unsupported field, inspect the generated request body before changing the images. If a required field is absent, inspect the mapping from the application asset record into inputs. If the request is structurally accepted but the resulting product is not represented as intended, the next investigation concerns product selection and creative requirements, not JSON field placement.
Keep these failure classes separate. A technically valid request can still produce an unsuitable fashion image. A visually excellent example from the old endpoint does not prove that the new endpoint will follow identical replacement rules.
The existing v1.6 category-scope guide remains useful for the older endpoint. The pose-preservation guide covers choosing the right kind of image-generation task. Neither replaces a request-schema migration.
Close with a versioned request contract
Evaluate any expansion into accessories separately. Changing the product category and endpoint together would make this request-contract comparison harder to interpret. No specific unknown-field error wording or silent-ignore behavior is assumed.
Record the old endpoint, new endpoint, old-to-new image mapping, removed fields, newly required fields, and the approved product/model source identifiers. Preserve one redacted request example for each version.
Exit migration preparation when every submitted field belongs to the selected endpoint schema and each input still represents the intended source. Record actual validation or output observations only after a separately authorized request; this article does not claim that one was executed.