V28.3 Release Notes

V28.3 Release Notes

Release: October 2026   |   Version: V28.3

Wilcom Embroidery Web API (EWA) V28.3 introduces changes to EMB output compatibility. Saving to EMB e4.2 (22.0) and earlier is no longer supported. Customers using these versions in their API recipes must update their output settings to ensure continued compatibility. This release also retains the file-security improvements introduced in V28.1.

Changes to EMB output compatibility

Wilcom Embroidery Web API (EWA) V28.3 no longer supports saving designs to EMB e4.2 (22.0) or earlier. Customers whose API recipes specify these versions must update their output settings to continue generating EMB files.

This restriction is enforced by the embroidery engine and applies to the design_version attribute of the output element in API recipes. Explicitly specifying an unsupported version does not bypass the restriction.

Unsupported output versions include e4.2, e4.1, e4.0, e3.6, e3.5, e3 and e2, as well as earlier EMB versions. Recipes requesting these versions may fail even if they contain only lettering and no uploaded EMB files.

Info
This change affects the EMB version used when saving designs. The existing file-security checks introduced in V28.1 continue to apply to uploaded EMB files.

Required recipe updates

Review the output element in your API recipes and shared templates. Replace requests for EMB e4.2 or earlier with a supported output version.

Recommended approach: Omit the design_version attribute to save in the latest EMB version supported by the server processing the request. Setting design_version to an empty value has the same effect.

Before – requesting unsupported EMB e3 output:

<output trueview_file="hoop_0_0.png"
        design_file="hoop_0_0.emb"
        design_version="Wilcom All-in-One Designs e3 (*.EMB)"
        dpi="150" />

After – saving in the latest available EMB version:

<output trueview_file="hoop_0_0.png"
        design_file="hoop_0_0.emb"
        dpi="150" />

If a specific supported EMB version is required, use the exact design_version value listed in the updated EWA Developer Portal documentation.

InfoThe design_version value must be compatible with the file format specified by design_file. This attribute applies to Wilcom native formats such as EMB, not stitch formats such as DST.

Error response for unsupported output versions

Requests specifying unsupported EMB output versions may fail with an HTTP 500 error. For example, a newDesign request specifying EMB e3 output returned the following response:

<error_info errorcode="120"
    message="Exception occurs inside CAD Server."
    cadcode="0x1D">
    <details>Call to EmbServer_GenerateDesign failed.
    Return code: 0x1D</details>
</error_info>

Similar failures have been observed with other unsupported EMB output versions.

If this error occurs after updating to V28.3, check whether the recipe requests EMB e4.2 or earlier. Update the output settings and retry the request.

If the error persists, contact Wilcom Support with the recipe and complete error response.

InfoThis error response is not exclusive to unsupported EMB output versions and may indicate other problems.

Deployment and customer validation

EWA V28.3 continues to use the existing API endpoint:

https://public.ewa.wilcomapps.com

As of October 13, 2026, the normal server group is running V28.3, while the auto-digitizing server group remains on V28.1.

The restriction on older EMB output versions applies to requests processed by V28.3. When design_version is omitted or empty, the EMB version saved depends on the server version processing the request.

Customers should complete the following checks when updating their integrations:

  1. Review recipes and templates. Update any design_version settings that request EMB e4.2 or earlier.

  2. Test design generation. Verify representative requests, including combined designs, lettering, and TrueView output where applicable.

  3. Verify file compatibility. Confirm that generated EMB files can be opened in the EmbroideryStudio version or other software used in production.

  4. Resolve legacy dependencies. If the receiving software requires an unsupported EMB version, contact Wilcom Support to review the workflow before resuming production.

Info
The EMB e4.2 and e4.1 output examples in the V28.1 release notes are no longer valid for V28.3. Refer to the updated Developer Portal documentation when specifying an EMB output version.